Brandon Rohrer (@brohrer@recsys.social)

Hey mastodon #networking and #linux folks, can I get your eyes on something? I wanted to make a beginner friendly guide for hosting your own static website, and I wanted to make it simple but secure.

Do you see anything boneheaded here? Or any best practices I left out?

https://www.brandonrohrer.com/hosting.html

Hosting your own website

Brandon Rohrer

Creating a web page is only the beginning. The business of sharing it with the world has a lot of
moving parts and a lot of choke points. If an ISP decides to stop traffic to your website or if your
hosting platform goes bankrupt there isn't a lot you can do about it. But what you can do is have a
solid Plan B — being ready to spin up another copy of your website on another server. A server that
you control, or at least a server of your choosing.

This guide shows one way to do set up your own hosting. It's not the only way or even the best way.
But it is at least a path through the desert.

Choose a computer

There are lots of cloud providers out there, of all sizes and in a lot of difference countries. Pick one.
Or use a computer you have at home, if your ISP will let you get away with serving a website from it.
| chose Digital Ocean because | had heard some good things about it and because it wasn't AWS.
The first step there is to create an account on Digital Ocean by setting up a "Team", even if it's just
you.

Add an ssh key

Create a public/private key pair on your local machine. Follow the Digital Ocean menus to

and follow the instructions there and here are some related docs .

It's recommended to create a passphrase for your keys, but don't forget to write it down.

ALT

1 0 0 View Post & Replies See Original

@brohrer great start!
Two things I’d hope to see in a future part of the guide are SSL (via let’s encrypt) and a little bit system hardening if necessary (I’m not sure how DO droplets are images by default).
But some conventional best practices that come to my mind that might also be relevant for a beginner: Setting a root password, disable password based logins via SSH, disable root login via SSH. Maybe turning on unattended upgrades.

0 0 0 View Post & Replies See Original