Parrot alternatives and similar software solutions
Based on the "Localization" category.
Alternatively, view Parrot alternatives based on common mentions on social networks and blogs.
7.8 10.0 L4 Parrot VS WeblateWeb based localization tool with tight version control integration.
5.3 7.2 Parrot VS AccentThe first developer-oriented translation tool. True asynchronous flow between translators and your team.
3.9 0.0 L3 Parrot VS ZanataZanata is a web-based system for translators to translate documentation and software online using a web browser.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Parrot or a related project?
Self-hosted Localization Management Platform built with Go and Angular 2.
NOTE: the project is no longer mantained, we suggest you look at traduora as an alternative.
- Built-in UI (web app) ready to deploy.
- REST API to easily extend or integrate Parrot into your pipeline.
- Export to various formats: keyvaluejson,
- Easily rename project strings, Parrot takes care of keeping locales in sync.
- Manage your project's team, assign collaborators and their roles.
- Control API Client access for your projects.
Building from source and try it out
Start out by cloning this repo into your GOPATH:
$ mkdir -p $GOPATH/src/github.com/parrot-translate/parrot $ cd $GOPATH/src/github.com/parrot-translate/parrot $ git clone https://github.com/parrot-translate/parrot.git .
Make sure you have Postgres running, by default Parrot's API server will look for it on
postgres://localhost:5432 and will try to connect to a database named
parrot. You can configure this using the AppConfig, see the configuration section below for more info.
To start a pre-configured Postgres instance on docker, simply run:
Now apply the database migrations. Using Alembic it's really simple:
$ cd migrations $ alembic upgrade head
Once again, if you wish to configure the DB parameters, you need to override the default values. For Alembic you just need to go to the
migrations/alembic.ini file and modify the
Finally you can build Parrot from source:
# From the root dir 'parrot' $ ./build/build-all.sh
Now we simply need start the API and serve the web app files.
Navigate to http://localhost:9990/api/v1/ping and you should be able to see if the API is up.
And on a separate terminal session, let's start a convinient Python HTTP server to serve the static web app files locally:
And to view the web app simply navigate to http://localhost:8080, it should open the login page of the web app.
At the moment, configuring the API app is only possible via environment variables. Here's the available options with their default values:
PARROT_API_PORT, default value: "9990" PARROT_DB_NAME, default value: "postgres" PARROT_DB_CONN, default value: "postgres://[email protected]:5432/parrot?sslmode=disable" PARROT_AUTH_ISSUER, default value: "[email protected]" PARROT_AUTH_SIGNING_KEY, default value: "secret"
You can also configure the Web App's backend endpoint by editing the file
parrot/web-app/src/environments/environment.prod.ts accordingly before building the Web app. Available options:
apiEndpoint, default value: "http://localhost:9990/api/v1"
This project is licensed under the MIT license.
The recommended medium to report and track issues is by opening one on Github.
Want to hack on the project? Any kind of contribution is welcome! Simply follow the next steps:
- Fork the project.
- Create a new branch.
- Make your changes and write tests when practical.
- Commit your changes to the new branch.
- Send a pull request, it will be reviewed shortly.
In case you want to add a feature, please create a new issue and briefly explain what the feature would consist of. For bugs or requests, before creating an issue please check if one has already been created for it.
*Note that all licence references and agreements mentioned in the Parrot README section above are relevant to that project's source code only.