TrumpetX

joined 2 years ago
[–] TrumpetX@programming.dev 1 points 1 week ago

Are you reading dungeon crawler carl too?

[–] TrumpetX@programming.dev 10 points 2 weeks ago (1 children)

I understand why some would do this. It's definitely a more secure setup, but I highly doubt "most". I like having passwords on my work laptop. I couldn't sync there with a VPN, for example. My wife, kids and parents aren't going to run VPNs on their phones, etc.

[–] TrumpetX@programming.dev 12 points 2 weeks ago (3 children)

Isn't that there point though? Remote synchronizing?

[–] TrumpetX@programming.dev 8 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

I have a 2013 MacBook running Ubuntu. No wifi drivers so I bought an Ethernet dongle off of eBay for $10. Runs immich pretty well.

[–] TrumpetX@programming.dev 10 points 1 month ago

This. This is the way. It solves this problem completely, but utilities somehow refuse it. It's almost like their argument is not in good faith ...

[–] TrumpetX@programming.dev 1 points 1 month ago* (last edited 1 month ago) (3 children)

What are you using for a reverse proxy? There's some nginx websocket settings I had to do before things worked properly. I use cloudflare, but just for the DNS/cdn stuff, not their zero trust things.

server {
  server_name my.domain.com;
  client_max_body_size 2048M;

  location / {
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_pass http://10.10.10.30:13378/;  # My Wireguard Tunnel up to the VPS
    # proxy_cache_bypass  $http_upgrade; # This was added by Certbot
    # WebSocket support
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
  }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/my.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/my.domain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = my.domain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

  listen 80;
  listen [::]:80;

  server_name my.domain.com;
    return 404; # managed by Certbot
}
[–] TrumpetX@programming.dev 10 points 1 month ago (2 children)

I don't disagree with you, but for a single server hosting multiple projects with differing system dependencies, docker is amazing. I've come around to using it for this practical reason.

Using docker over direct installation always feels like an unnecessary interface layer that just complicates things and introduces points of failure.

[–] TrumpetX@programming.dev 84 points 1 month ago (11 children)

This feels 1000% like a chatgpt prompt copy and pasted into a webpage.

[–] TrumpetX@programming.dev 2 points 1 month ago* (last edited 1 month ago)

OMG, me too!!

My aging S'14 has the rusting motor problem and it's not worth replacing (price to value.). So, I'm about 6 months away from needing a new electric.

The 6 looked really good. The slate would be my next choice, but I don't think it'll come out fast enough.

[–] TrumpetX@programming.dev 6 points 1 month ago

Why build one when you can build two at twice the price!

/s Contact quote

Seriously though, the cost was largely in the preparation. At some point you want to get more out of all that work. Yes, it was expensive for each actual launch. I wonder what the cost of stopping at the first one would have been. I'm WAGing that half the cost was getting there the first time. The other half was 5 more. That would be an interesting stat to know.

view more: next ›