Admin subdomains

[diveru4i]

Greetings.

Is there a way to properly serve wagtail admin site on a different subdomain (eg. admin.example.com)?

I've patched django-subdomains middleware so it would work with wagtail.wagtailcore.models.Site, but now all reverse urls in admin point to admin.example.com/--uri--/. To fix this I need to patch wagtail.wagtailcore.models.Page.url, but I just don't want to monkey-patch source packages.

Is there any way around that? And maybe in the future you could implement the settings.DEFAULT_PAGE_MODEL setting for wagtail, so we could override some default behaviour?

Thanks.

[gasman]

That's an interesting one! We intentionally don't include domains in the result of Page.url when there's only one Site record configured, so that links work immediately on a new Wagtail project without having to edit the site configuration. But that doesn't help if you're using multiple domains for hosting things other than Wagtail site entry points (such as the Wagtail admin)...

As a workaround, you could create a dummy site record (create a new page at the root level, and add a Site record in Settings -> Sites pointing to that page, using any hostname you like) - this will cause Page.url to always generate full URLs.

I guess the proper fix would be to add an "always generate full URLs" flag to settings - I can't see any more elegant way of handling this.

Re settings.DEFAULT_PAGE_MODEL, that's covered by issue #836. (No progress on it yet, though...)