Let's face it: setting up a server to run services useful for you and your community can be tiresome, difficult and not really satisfactory.
"Why not AWS services, Google cloud, Azure infrastructure and other professional, reliable solutions?", people would ask.
The answer is not easy, nor simple.
Running a server is a responsibility,
especially if you run it for a community of people trusting your services.
If you want to go for this adventure, let's have an overview of what you can expect - and you cannot.
In our experience, some of the key benefits of running a server are:
It's unrealistic to expect:
The goal of this documentation is to empower people that are not already experts to understand better how things work and be more informed when asking for help! Although we say "Do It Yourself", in essence it works better when you do it with others :-)
Panos wants to learn how to deal with a newborn server. Engineering background, GNU/Linux user, with no experience of sysadmin
K. wants to share what he learned about sysadmin. Literature and philosophy background, GNU/Linux user, with little experience of sysadmin.
Lennon, an HPE ProLiant Intel Xeon E-2224, 16 GB, Micro Server, located in the L200 Zurich space.