Skip to main content
Hostinger includes Chartbrew in its Docker application catalog. Use a VPS with the Docker template installed. Deploy Chartbrew on Hostinger This is an affiliate link. Chartbrew may earn a commission if you purchase a plan.

​
Before you start

You need access to your Hostinger VPS dashboard and, for a custom domain, its DNS settings. Use a new VPS or back up an existing server before you change its operating-system template.

​
Deploy from the catalog

  1. Open your VPS in the Hostinger dashboard and select Manage.
  2. Open Docker Manager, then the application catalog through Compose → One click deploy.
  3. Find Chartbrew and review its deployment configuration, image version, ports, and storage volumes.
  4. Complete the settings requested by the template and deploy it.
  5. Check the project logs and wait for database migrations and the client build to finish.
Hostinger documents the controls in its Docker Manager deployment guide. The template can change independently of Chartbrew releases; check the deployed version before you add production data.

​
Configure Chartbrew

Check that the project provides a Chartbrew database and Redis, or configure external services. Keep the template’s generated encryption key and database credentials. Save them with your backups. Set VITE_APP_CLIENT_HOST and VITE_APP_API_HOST to addresses your browser can reach. For a custom domain, use separate client and API hostnames. Follow Domains and HTTPS if you manage the proxy yourself. Avoid installing a second proxy on ports already used by your template. Use the Docker guide for environment values, persistent storage, and checks. If you deploy manually over SSH, follow that guide directly. Do not import the repository’s build: . Compose file as a standalone file: it also needs the source checkout and Dockerfile.

​
Check the deployment

Open the client URL, create your account, and complete the deployment checks. Check a scheduled refresh and an image export as well as sign-in. Before an update, back up the database, uploads, and configuration. For v5 installations, follow Migrate from v5 to v6.