Localize files that live in cloud storage rather than in a code repository.
Who this is for
Owners and admins.
Before you start
Google Drive and Dropbox connect by signing in and granting access. Amazon S3 is different: it uses an access key and secret you create yourself, plus a region and a bucket.
Steps
For Google Drive or Dropbox:
Open Integrations and pick the connector.
Start the connect flow and sign in to the storage account.
Grant transglot access.
For Amazon S3:
Open Integrations and pick Amazon S3.
Enter the access key and secret, the region and the bucket.
Save.
What happens next
The connector reads your localization files from the connected storage. Strings become ordinary keys in your project, and translations are written back as files.
Only what you connect is reachable: a connection is scoped to the account or bucket you named, not to everything the credential could theoretically see.
If it doesn't work
If a connector's card says it is not configured, this deployment has no client registered for it. That is an operator setting.
For S3, the region and bucket have to match: the address transglot talks to is built from them, so a wrong region reads as a missing bucket.
Related
The integrations hub
Which file formats can I use?