Sorry for scaring developers

Norwegian proot with a taste for shitposting Deeply sorry for my photoshop creation

Former account at Kbin

aspe:keyoxide.org:JYRRSWIKLZWX366Y4DONCIEYAE

  • 4 Posts
  • 135 Comments
Joined 5 months ago
cake
Cake day: June 7th, 2024

help-circle
  • I switched from duckdns about a year ago as it failed to resolve the addresses for my jellyfin server. I ended up buying a domain from cloudflare for 3 years for about $4, and I self-hosted ddns updater to automatically grab the dynamic ip, and set it to a subdomain.

    As for your nginx config, I’d imagine you could make 2 separate config files in sites-enabled that are nearly identical, but listen for different domains. Something like this:

    
    #config file 1 
    server {
        listen 80;
        server_name example_a.com;
    
        location / {
            return 301 http://example_c.com$request_uri;
    	#or use an ip instead of example_c.com
        }
    }
    
    #config file 2
    server {
        listen 80;
        server_name example_b.com;
    
        location / {
            return 301 http://example_c.com$request_uri;
    	#or use an ip instead of example_c.com
        }
    }
    
    
    #Or use "proxy_pass http://example_c.com;" in the location tag instead of "return 301..." if you want to reverse proxy the traffic
    
    












  • Funnily enough noone noticed that anything was “out of the ordinary”. The event organizer, who isn’t techy, asked to use my pc so he could transfer some assets for display, sent them over, right clicked the photoshop files, and opened them in a cracked photoshop program i installed using wine. He then proceeded to add some finishing touches and export them as png files without noticing this pc wasn’t running windows.

    The thing that caused the most hiccups wasn’t the os/software, but the hardware. The camera crew handed me some thunderbolt capture cards which didn’t work because my $300 laptop which I got for free didn’t support thunderbolt. We switched to some usb capture cards, and they worked perfectly without any configuring.

    So I guess Linux has reached the title of It just works™️ (at least for this use case)







  • The native resolution of that thing was something along the lines of 1500x1000, but the scaler only accepted 1920x1080, and 1920x1200. Both resolutions had the same top and bottom bars so we assumed something got disconnected during transit, and we didn’t bother fixing it as all content was in 16:9 anyways.

    For the pictures with hyfetch I just captured the display of the laptop in obs and forwarded it to the big screen as that was more convenient than fiddling with the terminal window on a screen I couldn’t see from laptop’s position.