![]() MRSK is intentionally designed around imperative commands, like Capistrano. You can see everything that's going on, it's just basic Docker commands being called.ĭocker Swarm is much simpler than Kubernetes, but it's still built on the same declarative model that uses state reconciliation. It's a fine option if you want to run on someone else's platform, either transparently like Render or explicitly on AWS/GCP, but if you'd like the freedom to move between cloud and your own hardware, or even mix the two, MRSK is much simpler. Running it yourself on your own hardware is not for the faint of heart. And the images built for MRSK can be used for CI or later introspection. Docker's layer caching also speeds up deployments with less mucking about on the server. You can boot a brand new Ubuntu (or whatever) server, add it to the list of servers in MRSK, and it'll be auto-provisioned with Docker, and run right away. No need to ensure that the servers have just the right version of Ruby or other dependencies you need. MRSK basically is Capistrano for Containers, without the need to carefully prepare servers in advance. Why not just run Capistrano, Kubernetes or Docker Swarm? You're probably still better off with a fully managed service if basic Linux or Docker is still difficult, but as soon as those concepts are familiar, you'll be ready to go with MRSK. Ultimately, MRSK is meant to compress the complexity of going to production using open source tooling that isn't tied to any commercial offering. When you're not locked into a single provider from a tooling perspective, there are a lot of compelling options available. Or you can buy the baseline with your own hardware, then deploy to a cloud before a big seasonal spike to get more capacity. You can have your web app deployed on several clouds at ease like this. This approach gives you enormous portability. Feed the config file a list of IP addresses with vanilla Ubuntu servers that have seen no prep beyond an added SSH key, and you'll be running in literally minutes. Whether that's low-cost cloud options without the managed-service markup from the likes of Digital Ocean, Hetzner, OVH, etc., or it's your own colocated bare metal. MRSK seeks to bring the advance in ergonomics pioneered by these commercial offerings to deploying web apps anywhere. Preferably before the bills swallow your business whole! If you want to run on your own hardware, or even just have a clear migration path to do so in the future, you need to carefully consider how locked in you get to these commercial platforms. But these are all offerings that have you renting computers in the cloud at a premium. And hosted Kubernetes is making things easier too on AWS, GCP, Digital Ocean, and elsewhere. These days we have excellent alternatives like Fly.io and Render. Heroku kicked it off with an incredible offering that stayed ahead of the competition seemingly forever. In the past decade+, there's been an explosion in commercial offerings that make deploying web apps easier. For subsequent deploys, or if your servers already have Docker and curl installed, you can just run mrsk deploy. If you're running multiple servers, you need to put a load balancer in front of them. If you're just running a single server, you're ready to go. Voila! All the servers are now serving the app on port 80. Prune unused images and stopped containers to ensure servers don't fill up.Stop the old container running the previous version of the app.Start a new container with the version of the app that matches the current git version hash.Ensure your app responds with 200 OK to GET /up (you must have curl installed inside your app image!).Ensure Traefik is running and accepting traffic on port 80. ![]() Pull the image from the registry onto the servers.Build the image using the standard Dockerfile in the root of the application.Log into the registry both locally and remotely.Install Docker and curl on any server that might be missing it (using apt-get): root access is needed via ssh for this.Connect to the servers over SSH (using root by default, authenticated by your ssh key).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |