# Working Swarm Deployment
**URL:** https://forum.gitea.com/t/working-swarm-deployment/5254
**Category:** Install/Maintain/Configure
**Created:** [May 21, 2022, 2:10pm UTC](https://forum.gitea.com/t/working-swarm-deployment/5254 "2022-05-21T14:10:22Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@engsys](https://forum.gitea.com/u/engsys)
#### Post date: [May 21, 2022, 2:10pm UTC](https://forum.gitea.com/t/working-swarm-deployment/5254/1 "2022-05-21T14:10:22Z")
I’ve used Gitea on other public instances and really love it. I’ve had some issues setting up Gitea in my swarm cluster. Namely once I deploy a basic stack with ENV VARS set for the url, features, etc it will take me to the install page. Even if I enter the URL for my public facing instance (ie [https://git.mydomain.com](https://git.mydomain.com)) it seems like it continues to want to listen on tcp:3000 and prefers that to be exposed.
As some context, I have this sitting in front of Traefik with both ssh ports and ssl ports setup for termination and passthrough to the backend.
My hopes were that I could find a working Swarm Gitea setup as a reference to unblock my efforts.
---
### Author:  [@lunny](https://forum.gitea.com/u/lunny)
#### Post date: [May 24, 2022, 12:28pm UTC](https://forum.gitea.com/t/working-swarm-deployment/5254/2 "2022-05-24T12:28:39Z")
I think you need a shared volume to store the configuration file of Gitea.