11
Support domain mapping for multisite
J
Jamie O
With Local 3.3.X there used to be a manual way that you could define SSL, .conf and hosts file entry so that a multisite could handle domain mapping. See https://localwp.com/community/t/local-router-error-message-on-multi-network-instance/1913/13 for details.
With Lightning, whenever the main site is restarted, the custom .conf added to ~\AppData\Roaming\Local\run\router are deleted.
At minimum, do not delete the custom .conf. More preferably, add a way to define related domains within the UI so that ssl, .conf and hosts entry are managed along with the main site by Lightning.
Activity
Clay Griffiths
Merged in a post:
Support Multisite with Domain mappings (custom nginx routes)
J
Jamie O
See https://localwp.com/community/t/local-router-error-message-on-multi-network-instance/1913 for good description of problem.
Goal:
Have a multisite instance running in local that handles routing for domain mapped environments. example.local as a multisite that can also serve childa.local, childb.local.
Ideal:
An option during site creation (or change) that lets you define a series of domains that a local site should serve up. It would address hosts file, ssl and config as a part of creation process.
MVP:
Additional Router Nginx config folder that would allow a custom folder within C:\Users\users\AppData\Roaming\Local\run\router\nginx\ to be read in on site start/restart. This would be checked for ssl and conf files that user has to manually generate (as well as self-modification of hosts file)
Alternative?
Some way to specify that certain .conf files should not be overwritten on start/restart.