admin/twenty
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
baaec81a91e680738989f2d52cbde13c0a34fc56
twenty/packages/twenty-docker/podman
History
Matt Drollette b1994f3707 Use correct env var name in podman-compose (#11858) 
The example .env file uses `PG_DATABASE_PASSWORD` so this makes it
consistent. Currently, the podman-compose directions will fail on first
run unless you manually change the env var name.
2025-05-04 12:23:02 +02:00
..
install-systemd-user-service
Added support for podman deployment (#11600)
2025-04-16 22:08:14 +02:00
manual-steps-to-deploy-twenty-on-podman
Added support for podman deployment (#11600)
2025-04-16 22:08:14 +02:00
podman-compose.yml
Use correct env var name in podman-compose (#11858)
2025-05-04 12:23:02 +02:00
README.md
Added support for podman deployment (#11600)
2025-04-16 22:08:14 +02:00
twentycrm.service
Added support for podman deployment (#11600)
2025-04-16 22:08:14 +02:00

README.md

How to deploy twenty on podman

DISCLAIMER: The k8s and podman deployments are not maintained by the core team. These files are provided and maintained by the community. Twenty core team maintains support for docker deployment.

How to use

  1. Edit .env file. At the minimum set POSTGRES_PASSWORD, SERVER_URL, and APP_SECRET.
  2. Start twenty by running podman-compose up -d.

If you need to stop twenty, you can do so by running podman-compose down.

Install systemd service (optional)

If you want to install a systemd service to run twenty, you can use the provided systemd service.

Edit twentycrm.service and change these two variables:

WorkingDirectory=/opt/apps/twenty
EnvironmentFile=/opt/apps/twenty/.env

WorkingDirectory should be changed to the path in which podman-compose.yml is located.

EnvironmentFile should be changed to the path in which your .envfile is located.

You can run the script install-systemd-user-service to install the systemd service under the current user.

./install-systemd-user-service

Note: this script will enable the service and also start it. So it will assume that twenty is not currently running. If you started it previously, bring it down using:

podman-compose down

Compatibility

These files should be compatible with podman 4.3+.

I have tested this on Debian GNU/Linux 12 (bookworm) and with the podman that is distributed with the official Debian stable mirrors (podman v4.3.1+ds1-8+deb12u1, podman-compose v1.0.3-3).