-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
"spin deploy": Allow deployments without CI/CD #75
Comments
Hey Jay as I played this feature a bit already I was wondering what it would look like when running multiple applications on the same server. As you won't deploy generic services like traefik and redis with each application/project, would you have like a generic stack/project with stuff like traefik, redis etc, and then specific app stacks with php service(s) + appropriate traefik labels? Or would this be meant to deploy 1 app per server? |
Been doing some testing, and got it working with multiple swarm stacks. 1 stack for traefik, 1 for redis, and 1 with a laravel project. What's cool about the setup is that it's really easy to run multiple web projects on the same server. Perhaps I'm misunderstanding the current situation and this is already possible, but I couldn't see how. A couple things I ran into:
Its also important to define the network as follows:
Else the stacks won't be able to communicate with each other. All things above are probably out of scope currently for this issue/feature, but it would be really cool to have proper support for multiple docker stacks. |
You can ignore my remarks, they don't really apply to the issue/feature in question. I'll create a separate feature request. |
Discussed in #61
Originally posted by jaydrogers January 24, 2024
馃憠 Describe the problem
馃懃 Problem evidence & reach
Some users have expressed interest in removing this requirement: https://discord.com/channels/910287105714954251/1195096786776359064
馃グ Describe the "impact" on users?
馃弳 How to solve this problem
Solution Overview
We can reduce the knowledge requirements by allowing users to run
spin provision
(to configure and prepare their server for Docker), thenspin deploy
to locally deploy their image to their servers.This proposed method eliminates a few headaches:
Deployment Process
docker image save
: https://nickjanetakis.com/blog/docker-tip-97-save-and-load-docker-images-from-a-zip-file)docker stack deploy
to initialize the transfer馃挴 How do we validate the problem is solved?
spin provision
(to configure their server) thenspin deploy
to deploy their stackThe text was updated successfully, but these errors were encountered: