3 ms·
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 p
by jayd16 7mo ago
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.
- skydhash 7mo agossh 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.
- mememememememo 7mo agoThe 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.
- NewJazz 7mo agoI could write a much more complicated list of steps for github.
- account42 7mo agoThe web is not the Internet.