serversideup/s6-overlay repository overview

Hi! We're Dan⁠ and Jay⁠. We're a two person team with a passion for open source products. We created Server Side Up⁠ to help share what we learn.

⁠Find us at:

• 📖 Blog⁠ - get the latest guides and free courses on all things web/mobile development.
• 🙋 Community⁠ - get friendly help from our community members.
• 🤵‍♂️ Get Professional Help⁠ - get guaranteed responses within next business day.
• 💻 GitHub⁠ - check out our other open source projects
• 📫 Newsletter⁠ - skip the algorithms and get quality content right to your inbox
• 🐥 Twitter⁠ - you can also follow Dan⁠ and Jay⁠
• ❤️ Sponsor Us⁠ - please consider sponsoring us so we can create more helpful resources

⁠Our Sponsors

All of our software is free an open to the world. None of this can be brought to you without the financial backing of our sponsors.

⁠Individual Supporters

⁠Available Docker Images

This is a list of the docker images this repository creates:

To make it easy for you, there are also other tags available to give you the best experience:

⁠Other options

Here are a few examples. We also have beta images and "edge" images for pull requests.

⁠What is S6 Overlay?

S6 Overlay⁠ is a process supervisor that allows you to make any app disposable and repeatable within one container, even if you need two processes to run it (like PHP).

Instead of running Supervisor⁠ inside of your container, S6 Overlay was built specifically for the lifecycle of containers -- giving you a more accurate way of bringing containers down and monitoring their health.

⁠Aren't you only supposed to run one process per container?

In a perfect world, yes. But this isn't a perfect world. See a great explanation called "The Docker Way" by the S6 Overlay⁠ team for an excellent explanation.

⁠Usage

Simply use this image name pattern in any of your projects:

serversideup/s6-overlay:{{flavor}}-{{version}}

For example... If I wanted to run Ubuntu 20.04, I would use this image:

serversideup/s6-overlay:ubuntu-20.04

⁠Updates

✅ The image builds automatically run weekly (Sunday at 0800 UTC) for latest security updates.

⁠Where do you host your stuff?

We get this question often. Our biggest principle is: your infrastructure should be able to run anywhere.

We believe privacy and control is the #1 priority when it comes to hosting infrastructure. We try to avoid the "big clouds" as much as possible because we're not comfortable that all 3 major players practice data mining of users and their products usually contain some sort of "vendor-lock".

We run all of our production servers on the latest LTS release of Ubuntu Server. The hosts we use are below. Some may be affiliate links that kick a few bucks at no extra cost to you, but they do not affect our recommendations at all.

⁠Vultr⁠

Our current favorite. Excellent performance and value. Lots of datacenter options too.

⁠Digital Ocean⁠

Lots of developer love here. Not the best performing servers, but they do have a lot of awesome products!

⁠Linode⁠

Great performance and great support. These guys have really enhanced their offering over the last few years.

⁠Benchmarks

If you're shopping for a host, check out the benchmarks we've ran →⁠

⁠About this project

We're taking the extra effort to open source as much as we can. Not only could this potentially help someone learn a little bit of Docker, but it makes it a heck of a lot easier for us to work with you on new open source ideas.

⁠Special thanks

• @shinsenter: Thanks for your previous contributions and providing examples to make our images better.

⁠Submitting issues and pull requests

Since there are a lot of dependencies on these images, please understand that it can make it complicated on merging your pull request.

We'd love to have your help, but it might be best to explain your intentions first before contributing.

⁠Like we said -- we're always learning

If you find a critical security flaw, please open an issue or learn more about our responsible disclosure policy⁠.

⁠Testing Github Actions Locally

If you want to test running Github Actions locally in development, we use Act⁠. After install, configure your ENV and then you can run:

act --secret-file .env [my-command]