By WilliamLucas
Couple of years back I started my Docker journey with CoreOS. While it made me go through a lot of painful transitions, because features of traditional OSes were missing (like no package manager, everything done with systemd config additions or containers) I got used to it and it runs very stable. The roling release system let me never have to think about painful reinstall due to major OS upgrades again. But not CoreOS is reaching the end of its journey.
With the sunset of CoreOS on the horizon, once Fedora CoreOS is out, I’m not sure where to go next. Migrate to Fedora CoreOS or go back to a classical OS.
I’m using it on a single host as my private server, for everything from web hosting, email server to vpn. Is that maybe something that a much simpler CentOS approach might also fullfil?
What the community take on this? Is CoreOS and it’s coming offspring viable for private, single node usage?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hello,
DigitalOcean does not enforce using SSL but it is recommended to always use that.
By default, MySQL server always installs and enables SSL configuration. However, it is not enforced that clients connect using SSL. Clients can choose to connect with or without SSL as the server allows both types of connections.
To tell MySQL to use mutual TLS and not just one-way TLS, we must instruct it to require client authentication to ensure clients present a certificate from our CA when they connect.
MySQL requires client certificates on a per-user basis. The requirement can be configured using CREATE USER or ALTER USER statements. When set, MySQL will reject connections from these users if they don’t present a valid certificate signed by CA.
With --ssl-mode=REQUIRED, clients require an encrypted connection and fail if one cannot be established. With --ssl-mode=VERIFY_CA or --ssl-mode=VERIFY_IDENTITY, clients require an encrypted connection, and also perform verification against the server CA certificate and (with VERIFY_IDENTITY) against the server host name in its certificate.
Hope that this helps. Regards, Priyanka
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.