Modules all depend on each other

[A. Wilcox]

Using the profile module requires the VPS and DNS modules. This is because profile pulls in VPS via "from panel2.vps.models import Node". vps/init.py pulls in vps.views. vps.views pulls in DNS via "from panel2.dns.views import is_valid_host", which of course dns/init.py pulls in everything.

I realise that this is pretty much how Flask blueprints are supposed to work by design, but the interdependencies should at least be better documented somewhere. It is annoying trying to rip out DNS management, i.e. for those who do not want to run a DNS service. The description of panel2 is "a modular framework", and I think it can live up to that, but a little work will be necessary.