From: Joe Doss <joe@solidadmin.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Wireguard not available for CentOS Stream
Date: Tue, 5 Jan 2021 12:14:22 -0600 [thread overview]
Message-ID: <3704c0e5-027b-d432-fb0d-4b0e3c93bcf8@solidadmin.com> (raw)
In-Reply-To: <CAH8yC8n-fC8MJxR7cA+otkqRyDZwhR7wz2Ni+-YTAgiKz7CRHA@mail.gmail.com>
On 1/4/21 3:55 PM, Jeffrey Walton wrote:
> From an admin and developer perspective I find Fedora Server a real
> gem. Speaking from experience, I would much rather work on Fedora than
> CentOS or Red Hat. Fedora Server comes with the latest stable tools
> and does not need things like Software Collections (SCL) to get a
> modern Apache, Python or PHP.
Same! I actually ran Fedora Cloud in production for 5 years at my
previous job across AWS and GCP with about 400 VMs. We did 6mo OS
refreshes and patching when needed. Fedora in production is super stable
for my use cases. We're using Fedora CoreOS at my current job now and
it's pretty great too.
Joe
--
Joe Doss
joe@solidadmin.com
next prev parent reply other threads:[~2021-01-05 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 20:17 Silvan Nagl
2021-01-03 21:31 ` Silvan Nagl
2021-01-04 1:24 ` Joe Doss
2021-01-04 12:47 ` Jason A. Donenfeld
[not found] ` <CAL0FmdWzknetT9raQcr_BhJwSWSBKPxXZocHSr2TT6bz2QihSA@mail.gmail.com>
2021-01-04 19:42 ` Joe Doss
2021-01-04 20:25 ` Bruno Wolff III
2021-01-04 21:55 ` Jeffrey Walton
2021-01-05 11:25 ` Jonathan Aquilina
2021-01-05 18:35 ` Joe Doss
2021-01-05 18:14 ` Joe Doss [this message]
[not found] ` <VE1PR08MB5837188C79F58A014916E123A0D10@53c70r.de>
2021-01-06 9:32 ` Silvan Nagl
[not found] ` <CAH8yC8n-fC8MJxR7cA+otkqRyDZwhR7wz2Ni+-YTAgiKz7CRHA@53c70r.de>
2021-01-05 13:06 ` Silvan Nagl
2021-01-05 13:56 ` Jeffrey Walton
2021-01-05 14:58 ` Toke Høiland-Jørgensen
2021-01-12 9:57 ` Christopher Ng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3704c0e5-027b-d432-fb0d-4b0e3c93bcf8@solidadmin.com \
--to=joe@solidadmin.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).