I earnestly wrote a couple of lines, and then a week later they replied that they don't have enough information to decide, at which point I just threw my hands up and decided for them. I don't need that kind of pedantic hoop jumping in my private life.
SpaceCadet
joined 1 year ago
I don't think it's possible with the current theming method.
broken window fallacy
Perhaps. It's a legal grey area here, not strictly legal but tolerated in certain areas (red light districts), but it's certainly not a socially acceptable thing.
It’s just really hard to believe a women asks if you’ve had sex with a sex worker…
I've been asked that question, and not just one time, so I believe OP that it can sometimes come up.
Love that the tesla coil comes straight out of Red Alert
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.
No worries, your input was helpful and informative anyway, so thanks.
Going with vhosts anyway seems to be the least cumbersome route at this point.
WEI is a proposed modification to Chrome/Chromium that doesn't even exist yet, and that would have the side effect of blocking adblockers on every site that implements WEI.
This here is an already existing change to the YouTube service that blocks adblockers on YouTube, across all browsers, Firefox included. It does not use or need WEI to do this.
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"
...
Oh he died soon enough.