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.
Overall, we can easily deploy new clusters thanks to the way we design our backend. We even aim to completely wipe out our production(s) cluster(s) with a new one every 3-4 months.
We are cloud agnostic and there is no vendor lock-in at FirePress.
Services in production (application deployed via containers)
- Ghost is the core application that clients use to manage their websites (Node.js on the backend)
- Caddy serves landing pages
- Traefik proxy
- Letencrypt
- Portainer
- Resilio
- rClone
- EKL
- Prometheus
- Grafana
DevOps | High level
- Digital Ocean, 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)
- Bash-script wrapping around Docker commands
- Python
- Cloudflare
- Backblaze B2 (Object store)