> Lots and lots of programmers have very little understanding and especially operation knowledge of how to host a public service. You can be an extreme graphics programmer and not know the web stack at all.

Can confirm.

Also, not everyone who wants to share content publicly has a domain name with which to do so, or the kind of Internet connection that allows running a server. If you include "hosting" by using a hosting provider... it's perfectly possible (raises hand) to not even have any experience with that after decades of writing code and being on the Internet. (Unless you count things like, well, GitHub and its services, anyway.)

On the other hand you probably don't need to go full k8s and datadog on it. Just host it. Use a PaaS so you don't need to do Linux admin.

I think both of you are misunderstanding what I proposed. You just need a single VM with an ssh server. Literally no web service needed, if all you want to do is host some code remotely.

I didn't misunderstand. Sshd is a web service. Most folks don't already know how and don't want to set up a machine that is always on, that will restart on power loss, that will have a static IP or dynDNS, with a domain name and proper routing and open ports and certs and enough bandwidth and that's before you even worry about actual security and not just what is needed to work.... It's actually a big annoyance if you don't do it all the time.

ssh isn't a web service (some would argue that smtp and ftp aren't too as they came before the web).

And I believe GP was talking about the only thing you need is:

  ssh user@remotehost git init --bare repo.git

And then you can add the remote to your local repo with

  git remote add origin user@remotehost:repo.git

Now all you need to do is

  git push origin branch_name

Replace origin with another identifier if it's already taken.

The rest of the owl: go to provider, set up VM (20 questions) log into root. SSH for login. set up firewalls. create non-root user. useradd or adduser? depends if you want a home dir I guess. debug why you can't ssh in. Finally get in. sudo apt update. sudo apt install git (or is it named something else?). install failtoban. install fw.

then do above.

then troubleshoot.

set vm backup policy.

save myriad passwords and secret to bitwarden.

get ubuntu to stay up to date.

I could write a much more complicated list of steps for github.

The web is not the Internet.

VM and ssh. Needs linux admin exp. Security updates. Understand how to securely connect from an IP without opening 22 on 0.0.0.0/0

Opening ssh to the internet is fine if you are using key based auth, which is the default on many VM setups.