Accent - Translation and Localization Management

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Overview

Accent is an open source, developer-oriented translation and localization management platform. Developers sync an application's translation files in and out through an API and CLI, and translators manage, review, lint and collaborate on strings through a web UI, with version history and a review workflow. Under the hood Accent is an Elixir and Phoenix GraphQL API backed by PostgreSQL, with a compiled web frontend. This AMI delivers Accent installed and secured so a working translation platform is operational within minutes of launch.

## Why This Image vs a Manual Install

Accent ships as an Elixir OTP release whose JavaScript frontend is a build artifact absent from every source tarball, and it has no built-in password authentication of its own: out of the box its only zero-configuration login is a password-less provider that would leave a public instance completely open. Running it safely yourself means sourcing the correct compiled image, standing up PostgreSQL, generating the Phoenix signing and encryption secrets that upstream ships as published defaults, and putting an authenticated, encrypted front door in front of it. This image completes every one of those steps at build time. Accent runs the official upstream container unmodified and binds to the loopback interface only; PostgreSQL is never exposed on a host port; a per-instance web credential, PostgreSQL password, Phoenix secret key base, session signing salt and encryption vault key are all generated on each instance's first boot; and an nginx reverse proxy terminates TLS on port 443 with a per-instance self-signed certificate and enforces HTTP Basic authentication.

## Authentication and Single Sign-On

Accent has no password authentication of its own; every real single sign-on method (GitHub, GitLab, Google, Slack, Discord, Microsoft or any generic OIDC issuer) requires your own OAuth application credentials, which cannot be baked into a shared image. This image therefore ships with the front door gated by a unique per-instance HTTP Basic credential over TLS, and Accent listening only on the loopback interface behind it, so the instance is never an open, unauthenticated application. The paired deployment guide documents how to register an OAuth or OIDC application with your own provider and then retire the basic-auth gate.

## Security Hardening

This image follows a defence in depth approach:

• No default or shared credentials: the Phoenix secret key base, session signing salt and encryption vault key that upstream ships as published defaults are never used; a unique value for each is generated on every instance's first boot
• Per instance secrets: the web credential, the PostgreSQL password and the self-signed TLS certificate are all generated per instance on first boot, never shipped in the image, and written only to a root-only file
• No open sign-up: the front door is closed by a per-instance HTTP Basic credential, so a scanner or passer-by cannot reach or self-register with the password-less provider
• Network isolation: Accent binds exclusively to the loopback interface; PostgreSQL is never published to a host port; only the nginx TLS reverse proxy is exposed
• Encrypted front door: nginx terminates TLS on port 443 with a per-instance self-signed certificate; plain HTTP on port 80 redirects to HTTPS
• Dedicated data volume: the Docker data root and the translation database live on their own disk, surviving OS-disk changes and resizable independently

## Concrete Use Cases

• Centralize an application's translations: give developers an API and CLI to sync translation files in and out of source control, and translators a web UI to manage, review and lint every string, with version history and a review workflow
• Continuous localization in CI: push new source strings from a build pipeline into Accent and pull translated files back out at release time through the file sync and export endpoints, keeping every locale in step with the codebase
• Team translation and review: collaborate on strings across a team with roles, comments and a review workflow, using the bundled grammar and spelling checks to catch errors before they ship

## AWS Integration

Deploy on any EC2 instance type; the recommended size is m5.large. Terminate TLS at an Application Load Balancer with your own certificate, or keep the per-instance self-signed certificate. Back up the translation database using EBS snapshots or AWS Backup, and resize the dedicated data volume independently of the OS disk as your string catalog grows.

## cloudimg Support

24/7 technical support by email and chat. Help with deployment, wiring up your own OAuth or OIDC single sign-on and retiring the basic-auth gate, reverse-proxy termination with your own domain and certificate, and backup planning for your translation database.