When working with localized content in an agile, continuous deployment environment, it is critical to optimize for translation speed. The Repository Connector is designed to shorten the time it takes to translate new content by automatically pushing changes to resource files in a repository to the Smartling dashboard and pushing new translations back to the repository. Read more there.
REPO_URL- Url to the repository
REPO_ALIAS- Alias for the repository. This is used as a prefix for file uri in Smartling (default is
SVN) Repository type (default is
REPO_PROJECT_ID- Smartling project API credentials, available from the Smartling Dashboard
REPO_PROJECT_KEY- Smartling project API credentials, available from the Smartling Dashboard
REPO_POLLING_SCHEDULE- Polling schedule to determine how often the connector checks for changes in the repository (default is
0 */5 * * * ?)
REPO_USER- Repository user name
REPO_PWD- Repository password
REPO_CALLBACK_URL- Url for translations callbacks. This url must be available from internet. Optional, default is empty string
REPO_CHECK_TRANSLATIONS- Polling schedule to determine how often the connector checks for updates to translation status in Smartling (default is
0 */4 * * * ?)
There are two DEMO images: SINGLE - easy configuration for one repository, VOLUME - image that references external folder from docker machine as a configuration one.
Only one repository can be configured using environment variables. Submissions, logs and metrics are persistent on container level.
$ docker run -it -e REPO_URL=https://github.com/xxxx \ -e REPO_USER=**** -e REPO_PWD=**** \ -e REPO_PROJECT_ID=**** -e REPO_PROJECT_KEY=**** \ -p 5555:5555 dmitriy/repo-connector
The image allows to map a directory from the docker machine as a configuration folder for repo-connector. You can define several repositories with the image. And keep logs, metrics and submissions between containers.
$ docker run -v $(pwd):/usr/local/repo-connector/cfg -p 5555:5555 dmitriy/repo-connector