• 1 Post
  • 35 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle

  • Yeah I remember those early days. KDE had a 1.0 version out in the late 90s, which was perfectly usable as a standalone desktop environment, while at the same time Gnome was little more than a panel with a foot. Early Gnome was an unholy mess and remained so until the late 2.x versions in the mid 2000s. Like how many window managers and file managers did they go through? I believe they even had Enlightenment as the default window manager for a while, and then there was that weird Ximian desktop phase.





  • I don’t think that’s the case anymore.

    I just checked, the time in the UEFI BIOS is in UTC, yet both Linux and Windows 10 display the local time correctly as an offset to UTC. I didn’t have to do anything special for that.

    Edit:

    So I looked a bit deeper into it, and this is apparently controlled by a registry key called RealTimeIsUniversal in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]. You can paste the text below in a .reg file and then import it to set the parameter:

    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
    "RealTimeIsUniversal"=dword:00000001
    

    I confirmed that this setting exists on my system, but I have no memory of ever manually setting this parameter. It’s documented in the Arch wiki though, so it’s possible that I did set it and forgot about it.

    In any case, if you do a fresh Windows install and your time differs between Linux and Windows , this is what you should check.








  • You can use the wildcard domain

    Yeah the problem was more that this machine is running on a network where I don’t really control the DNS. That is to say, there’s a shitty ISP router with DHCP and automatic dynamic DNS baked in, but no way to add additional manual entries for vhosts.

    I thought about screwing with the /etc/hosts file to get around it but what I ended up doing instead is installing a pihole docker for DNS (something I had been contemplating anyway), pointing it to the router’s DNS, so every local DNS name still resolves, and then added manual entries for the vhosts.

    Another issue I didn’t really want to deal with was regenerating the TLS certificate for the nginx server to make it valid for every vhost, but I just bit through that bullet.



  • I was afraid it was going to come down to that. I have been looking into configuration options for the apps, but they’re 3rd party nodejs apps and I know jack shit about nodejs so I’ve had no luck with it so far.

    Going with vhosts anyway (despite the pains it will create on this setup) seems to be the preferred way forward then.

    Thanks for the insight, and for confirming what I already suspected.



  • Hmm no, that’s not really it… that’s more so that you don’t pass URLs starting with /app1/ onwards to the application, which would not be aware of that subpath.

    I think I need something that intercepts the content being served to the client, and inserts /app1/ into all hardcoded absolute paths.

    For example, let’s say on app1’s root I have an index.html that contains:

    ...
    src="/static/image.jpg"
    ...
    

    It should be dynamically served as:

    ...
    src="/app1/static/image.jpg"
    ...