What kind of Back-End drives FirePress
If you are curious about how things work like I am, I bet you will enjoy this post. I'll share the core elements that make FirePress an actual product you can use to grow your brand on the Web.
If you are not sure what FirePress is at this point, please check out our About section first.
Services in production (application deployed via containers)
- Ghost is the core application that clients use to manage their websites
- Node.js on the backend
- Backbone.js on the frontend
- Nginx serve landing pages
- Percona (MySQL)
- Traefik proxy
- Undisclosed monitoring vendors
Services | Exploration in progress
DevOps | High level
- Linux servers on Ubuntu 16.xx
- Cloud vendor (undisclosed at the moment)
- Micro services architecture
- Docker Swarm Orchestrator(Moby project)
- Well, you already understand that we deploy things in containers at this point.
- Container OS: Alpine (mainly), Debian
- Bash-script wrapping around Docker commands
- Backblaze B2 (Object store)
Overall, we can easily deploy new clusters thanks to the way we design our backend. We even aim to completely swipe out our production(s) cluster(s) with a new one every 3 months.
We are cloud agnostic and there is no vendor lockin at FirePress.
Operational | High level
- Slack web hooks to monitor our backups and core operation on the cluster
- Github (public stuff)
- Gitlab (private stuff)
You probably know that Ghost is an open source project. But did you know that Ghost is #82 while WordPress is #509 of all GitHub projects (ranked by stars)? To put things in perspective (as per April 25th 2017):
19, Moby (Docker)
P.S. If you have solid skills 🤓 with Docker Swarm, Linux and the things mention here and you would love 💚 to help a startup to launch 🔥 a solid project, I would love to get to know you 🍻. Buzz me 👋 on Twitter @askpascalandy. You can see the things that are done and the things we have to do here.