Regarding swarmpit, how does load balancing works in Swarmpit ,
Should we mention each port for each replica in docker compose yml or mentioning a single port will also help , please suggest.
You should always have just one replica of swarmpit ..
Swarmpit is management tool so short outage is ok .. Swarm is going to redeploy new instance almost immediately because of default restart policy ..
@rwestbrookjr hi finally yes :)
I've been through a baptism of fire with containerisation - happy to help anyone here with traefik, gluster, loads of stuff
@nohaapav is it 'AutoRedeploy' on the service definition?
that way your CI doesn't have to have access to your infrastructure to deploy new version
btw. we're planning to have some recommended example compose files of traefic and stuff to get you started in repo, did you setup traefik 2.0 ?
also - I see the 'View Logs' on services, is there a way to run a command - like bash to get into a running container?
perhaps a little off topic but... one postgres per app database or one shared postgres container with multiple app databases?
shared container pros: easier to manage, backup, replicate. Cons: single point of failure (all apps down if pg container goes down)
per app postgres pros - resilience/app isolation; Cons: different versions, more stuff to maintain, replicate
How do you decide?
@mhsutton_gitlab scaling is possibly the concern for pointing all your apps at the same db instance. If the load from your multiple apps is easily served by a single postgres instance, this might be desired due to the management pros you shared. As your load grows over time, you could always spin up another db instance and migrate data for one of your busy DBs into it and re-point apps.
@mh720 yeah - really good point, unfortunately instance scaling is not an option yet (because persisted volumes are too slow) and actually having more replica nodes makes no difference to capacity. I think what you outline is the only way to share the load. Which is not a bad option, things will have to have gotten seriously busy though. The replica stuff already provides replication on servers in a different geo-zone
@mh720 thanks for the response
version is 1.5. How to upgrade the version of Swarmpit ?
E.g. to upgrade to 1.7 This one:
https://github.com/swarmpit/swarmpit/blob/1.7/docker-compose.yml
https://github.com/swarmpit/swarmpit/blob/1.7/docker-compose.yml
Of course update just deltas -> versions, and things that were introduced since 1.5
or it is just limited to anonymous and named volumes?
Hey guys, I was looking for a Rancher 1.6 alternative to use with https://appwrite.io and Rancher 2.0 seems to have lost the simplicity first approach by putting all the cards on Kubernetes (which seems to me like an overkill for most small to medium companies or apps). I tried Swarmpit over the last few days and really liked how simple everything was. Is swarmpit production ready? is there any public roadmap available?
@eldadfux Hi Eldad. Yes, we run Swarmpit in PROD for our internal infrastructure, fintech and so on. As you mentioned: Swarmpit/Swarm is aimed for small/medium companies and startups tired of complex solutions in the era of rapid development.
You can find ROADMAP here: https://github.com/swarmpit/swarmpit/blob/master/ROADMAP.md
We'll update info regarding 1.9 RELEASE soon as well as landing page.
You can find ROADMAP here: https://github.com/swarmpit/swarmpit/blob/master/ROADMAP.md
We'll update info regarding 1.9 RELEASE soon as well as landing page.
this one is stored in swarmpit DB
To use swarmpit API go to settings section and generate API token.
