Unique app name error problem when building a Wagtail multisite solution

[Matthias Brück]

Hi all,

I want to build a Wagtail multisite solution and I'm running into problems with unique application labels. I would like to have the following project structure:

project

  |

  |--app1

  |    |--core

  |    |--pages

  |    ...

  |--app2

  |    |--core

  |    |--pages

  |    ...

Even when i try to set the name in `apps.py` to unique ones i still get the unique name error. 

Is this project structure somehow possible?

I understand that you would commonly put app2 in a separate project. 

But how would you do it if you implement a Wagtail multisite solution and still want to keep things separated?

Thanks!

Matthias

[Matthias Brück]

is this really just not possible? What I found is this: 

you can't have two apps with the same name, even if they have different fully qualified module paths

https://groups.google.com/forum/#!msg/django-users/AMYLfQo6Ba4/Y-57B0i7qy4J

How would you guys handle this?

[Melvyn Sopacua]

Hi,

On Wednesday 21 December 2016 14:30:32 'Matthias Brück' via Django users
wrote:

By picking the right tool for the job. Judging from 1.8 Release notes,
Wagtail is working towards multi-tenancy, but isn't there yet. So, pick
a different CMS (for example Mezzanine) that is. Especially one that
uses the multi-tenancy that is built-in to django through the sites
module.
Don't work against the flow :)
--
Melvyn Sopacua

[Matthias Brück]

Hi Melvyn,

thanks for your answer. Unfortunately switching the CMS isn't an option. And even if I skip the multisite requirements i could think of usecases where it might be a problem in just a django project as well, wanting to have a similar project structure, doesn't it?