nickjj
commented
9 years ago Hi, thanks for showing interest in the project.
1) At this point I'd say it's production ready.
2) Yes, but I don't feel comfortable linking my client's sites here. I am using a modified version of this code base to run https://buildasaaswithflask.com/ , which is a site that sells and securely distributes screencasts that teaches you about this code base.
In the above link's case, it's using 1 time payments instead of monthly recurring subscriptions and given the current base of this project, that only took a few hours to implement and test.
3) I'm not sure what you mean here, but every service is its own Docker image. This allows you to easily scale and move running containers around.
4) You can comfortably run everything on 1 server with a single $10/month Digital Ocean droplet. You will have a few hundred mbs of RAM left over to cache your important data and have breathing room.
5) The deploy aspects of everything can be found in this book https://leanpub.com/deploy-web-apps-with-docker, it does not cover multi-instance scaling but there are a number of easy to use command line tools to create a new droplet or you can just use Digital Ocean's website's UI when needed because really, you pick 3 things and click a button and 30 seconds later you have a new droplet. You can also easily add more CPU/RAM/disk to a droplet (~20-30 seconds).
You're also not locked into using Digital Ocean, nothing is specific to that platform. If you really need auto-scaling you could just move to Amazon.
6) No, that goes well beyond the material I plan to cover because to make something like this generic is a pretty huge undertaking but you could build on other open source technologies like kubernetes, mesos or openshift v3 and adapt them to your company's needs.
7) If you're talking about users picking new plans in the app contained in this source code, then yes. After you've signed up with an initial plan you only need to click 1 button to change plans and the user's billing gets pro-rated automatically. They don't even have to put in their billing info again to change.
8) The deploy example is based on using 1 host. Docker itself handles DNS in situations like this for container to container communication. Also host to container is easy too because it's just localhost.
I hope that answers your questions. The main website that sells the screencasts will get a new video posted today or tomorrow that will demo most of the capabilities of the application.
PhantomYdn
Hello,
We've just started looking for ways to provide our solution (Orienteer) as a service. Your project looks great and seems to be exactly what we needed in! But there are several questions:
1) What is the status of this project? Is it recommended for production or not yet? 2) Are there any projects which use this solution? Could you please share some links? 3) Does solution support plans which based on different Docker images? 4) Does solution support plans which based on different limitations (RAM, SSD)? 5) Can solution automatically buy additional hosts in digital ocean if required? 6) Does solution provide API for automatic provisioning and activation of a service? 7) Does solution support smooth switch of a plan? 8) Does solution support automatic assignment of DNS per deployed app?
Thanks for your great project!