Hacker News Reader

Comment by debazel | Hacker News Reader

This combined with "Always Open Site in Container", that pins a site to a specific container makes it almost invisible to me when moving between profiles.

I have several sites I only want to open with specific profiles and this workflow is a pain with Chrome. (click link with wrong profile, copy url, close tab, open a new browser, select profile, paste url, open site with correct profile.)

View on HN

I really like the "Always Open Site in Container" along with "Limit to Designated Sites" once it's set up, but I wish there was a way to make it accept wildcards otherwise I have to manually add localhost:8080, localhost:8081, etc. Manually adding a dozen or more becomes painful.

Does the Containerise extension do what you want? I've used it in the past for wildcard subdomains but not for ports.

https://addons.mozilla.org/en-US/firefox/addon/containerise/

I have come across that one, but not having the "trusted" badge in the extension store has usually been a hard pass for me. I might reconsider.

It’s so odd that there is no way to edit the list of sites manually. Now, the only way to ”Always Open Site in Container” is to first browse to that page. That’s not just inconvenient for batch edits, what’s worse is that you can end up in a redirection deadlock, with no chance to edit which container the first url should open in.

I find that for dev workflows (even outside firefox containers) to not mix up badly, you end up needing to split localhost anyway - so for example, binding to specific IPs inside 127.0.0.1/8 (it's a whole /8, you're usually not running out of that), or, depending on how badly you need ::1/IPv6 bindings, service.localhost6 or service.localhost6.localdomain6 style names instead of just localhost.

Reply on news.ycombinator.com