I had already tried Yunohost several years back, it was not good enough to my liking, there was not enough applications avaiblable and my self hosted services were not that messy yet.
It was still a few web apps hosted on a virtual machine.
I have had a plan in mind for several months, better yet years: regroup all my applications, install a ldap server, make beautiful playbooks to deploy and manage all that stuff but that represented a mountain of work, skills to acquire, hours to spend (24 hours in a day is far too little)… I did not have the motivation to do it.
Then a few months ago I gave another shot at Yunohost and saw it as a solution to all my problems:
One simple way to install all the apps
One simple way to backup all the apps
A central user directory
A simple way to manage the updates
All that was left to do was choose where to host it and how to proceed.
The where, was quite simple: I already had two dedicated OVH servers.
As for the how, I first thought about lxc (well, lxd in fact) but I quickly understood that it was not going to work, at least not without some tweaking.
Ynh does some of its magic by mounting and unmounting filesystems, that does not fit well with containers.
So I chose virtualization, that’s what I had done on one of my dedicated servers.
It brings flexibility, being able to make a whole system snapshot before heavy maintenance operations is quite nice.
This time I would choose KVM over Esxi since I had grown quite accustomed to it over the years.
I chose to use two virtual machines, one for a test instance and one for my production.
Each one available on a dedicated IP, thanks to OVH IP failover.
I explain how to do it in another article of this blog.