I read this post which would answer part of my question: How to setup client ownership of domain name and hosting
In that question, the asker wanted to know how to make sure ownership of the domain/hosting is handed off to the client so that person wouldn't have to manage it indefinitely. I have a similar question:
I mostly work for organizations having at least one or two IT departments of their own. Oftentimes, they have their own servers. However, not all clients have their own infrastructure. For instance, let's picture the following client:
- The client is a very small business or non-profit organisation, or is a standalone person
- The client is non-technical
- The client has no server infrastructure.
In this case, if you create a Drupal/Wordpress/etc site using a panel, it will be fully managed after server downtime or hardware failure. It will just restart and work. The backups are taken care of by the hosting provider.
But what if, lets say, you'd rather use Django or Play Framework? This requires more complex tooling. For instance, I'll need the following items:
- Console access, with sufficient privileges to set up the server.
- I'll need to take care of inittab setup, so the application restarts in case of trouble. I'll need to be root.
When using something like Django or the Play Framework, will using something like inittab be enough to allow me to disengage from the client and not have to maintain the system? If I want to disengage, must I use a major panel created CMS or will the above plan work?