I am about to set up a cloud instance with linux operating system, and the common choice here normally would be ubuntu. But since they failed their newest release, and I have the option of going fedora or debian. What would you guys recommend for server?
Github has zero 9’s so at this point just use Arch for everything fuck it
(I would personally recommend Debian)
Slackware, be bold.
Both Debian and RHEL-like distros are solid choices. Both are super stable. Debian tends to not always have the newest packages, so if you want that I’d steer away from Debian. Personally I use Rocky Linux for my servers. It’s based on RHEL, meaning each new major version benefits from Red Hat’s 10 years of software support. Debian (and derivates) have better community support I think, but RHEL has very solid documentation (which for the most part applies directly to Rocky, Alma etc.)
Here’s a great article outlining the differences between Alma and Rocky.
But for something simple like running a Go application, both should work just fine, so choose what you’re most comfortable with.
Rocky is available at Scaleway too.
Debian is a great pick. It’s stable and has a great support community.
Best fit is always dependent on how you’re planning to use it. Find out what your requirements before you set up a server.
Generally Debian is chosen very often, but I’d wager pretty much any distro will do. Your own experience goes a long way in making a distro a good choice.
It is going to run af .go application that is the backend for my website. Handling user logins, database translation etc.
Go applications are statically built. So you don’t really need anything special on the server for that. Anything will do. Debian would be fine here.
Debian would be the most obvious choice. Perhaps Alma is also a good option. If you would like a european option, OpenSUSE leap can also do the job.
Do yourself a favor and go with Nixos. Dive head first into to the rabbit hole and set up a repeatable and immutable system. You’ll thank yourself later when so many maintenance tasks become a GitOps workflow: update config, commit, push, build, deploy, rollback if it fails
Thank you!
DEBIAN
Denian Stable. It just works.
Professional as in an organisation? You should probably start by gathering functional and non-functional requirements from stakeholders.
It’s for running a .go app as a backend through an api to my website/app frontend.
Which reverse proxy?
how common is ubuntu on servers?
Much more common than is should be.
I’ve seen mostly RHEL in professional server environments.
My AI says I should always choose Debian 12 (last stabel) instead of 13 (latest build). Is this still a thing? Not hosting applications that needs to be reliably run on latest builds?
arch linux btw
