4 ms·

If you think that's bonkers, I'll give you an even worse idea: a dedicated desktop machine. I have a dell optiplex running Intel i3-2100 with 8GB RAM and 1TB Sa

by mcny 6y ago

If you think that's bonkers, I'll give you an even worse idea: a dedicated desktop machine. I have a dell optiplex running Intel i3-2100 with 8GB RAM and 1TB Samsung 860 Evo SSD. No display. Fedora runs like a dream with dnf automatic. Use cockpit if you'd like. You can use your windows or Mac laptop with visual studio code to do web development. ng serve works as if you ran it from your laptop. The biggest drawback I can think of is if you ever needed to leave the house. Thankfully, I have no life so I don't have this problem.

cassianoleal 6y ago
> The biggest drawback I can think of is if you ever needed to leave the house. Add ZeroTier to the equation and as long as you have Internet connection when you're outside the house you'll probably not even notice it.
Tsiklon 6y ago
Having both your laptop and desktop on a WireGuard vpn with the gateway on your choice of cloud host would solve that problem, also it would solve having to deal with wandering IP addresses as you may find with a home internet connection
rovr138 6y ago
I see WireGuard and ZeroTier mentioned. I just use ssh. SSH to a VPS and map 22 to a port on the VPS. I have a really small VPS for this.
- mcny 6y ago
  I think the reason they mentioned more complicated setups is because I'm using an actual old machine at home and unless you know what you're doing you don't want to expose it to the world. I think poking a hole on port 22 is mostly ok if you only allow key authentication and no password authentication but I don't know enough to give advice on security.
  - rovr138 6y ago
    Just posting alternatives. I use a VPS with SSH. I have to ssh in, then I can ssh into the machine at home. For safety, key authentication and fail2ban would cover a lot. I mainly have the 1 port. If I need to expose another SSH port to the internet, I can do it, but yes, it would need extra protection since logs are coming from the machine ssh'ing in.
    - hiq 6y ago
      > For safety, key authentication and fail2ban would cover a lot. I mainly have the 1 port. Changing the port from the default 22 to something else is also recommended, if only because it makes fail2ban logs way less verbose.

by mcny 6y ago

cassianoleal 6y ago

> The biggest drawback I can think of is if you ever needed to leave the house. Add ZeroTier to the equation and as long as you have Internet connection when you're outside the house you'll probably not even notice it.

Tsiklon 6y ago

Having both your laptop and desktop on a WireGuard vpn with the gateway on your choice of cloud host would solve that problem, also it would solve having to deal with wandering IP addresses as you may find with a home internet connection

rovr138 6y ago

I see WireGuard and ZeroTier mentioned. I just use ssh. SSH to a VPS and map 22 to a port on the VPS. I have a really small VPS for this.

mcny 6y ago
I think the reason they mentioned more complicated setups is because I'm using an actual old machine at home and unless you know what you're doing you don't want to expose it to the world. I think poking a hole on port 22 is mostly ok if you only allow key authentication and no password authentication but I don't know enough to give advice on security.
- rovr138 6y ago
  Just posting alternatives. I use a VPS with SSH. I have to ssh in, then I can ssh into the machine at home. For safety, key authentication and fail2ban would cover a lot. I mainly have the 1 port. If I need to expose another SSH port to the internet, I can do it, but yes, it would need extra protection since logs are coming from the machine ssh'ing in.
  - hiq 6y ago
    > For safety, key authentication and fail2ban would cover a lot. I mainly have the 1 port. Changing the port from the default 22 to something else is also recommended, if only because it makes fail2ban logs way less verbose.