Closed dxlr8r closed 4 years ago
I wouldn't use the feature, but sure why not. I believe it should be a setting though and not default behavior. That would make it dependent on #76 and future development to introduce settings
Awesome!
Oh, a question before I get on this @dxlr8r, are you assuming the created container will be destroyed or do you want it to persist?
Good question @LoveIsGrief . I guess it would be ok to destroy them, if no page with that url is no longer open, and if it doesn't have any customisation (added domains, etc.).
OK, that makes it quite similar to a temporary container. And another question: what do you expect of subdomains?
For example should google.com
create a google.com
container and mail.google.com
create another? Or should they both resolve to google.com
and end up in the same container?
And another question: what do you expect of subdomains?
Good question. Maybe have that as an option? Personally I think I'd like to have subdomain under the same temporary container as the top domain.
OK, I'll have to check how to implement that :slightly_smiling_face: I believe I have all the information now. Should you have more precise thoughts on the matter, Don't hesitate to utter them :slightly_smiling_face: Thanks for the responses.
Just stumbled a cross this gem. As the subject says, if the domain isn't already added to a container, create a new container with the name of the domain and add the domain to that container.