All geek questions in one place

Django SAAS Projects

I almost finished the development of the Django project (with several plug-in applications).

I want to propose this project as SaaS (something like 37signals.com).

ie: customer1.product1.com, customer2.product2.com, etc.

product1 may be basecamp product2 may be high etc.

I want to know how the project should be structured for these products.

If there is one project, according to which all products will be an application. ---- OR ---- Do I have to do different projects for all products.

There are also database gaps .. all products will look in one database or we must have separate databases for each product.

I am looking for the most efficient and scalable way to do this.

thanks

+3
source share
3 answers

If you want applications to interact in some way (e, g, exchange user accounts), they must be in the same database. As long as Alex Gaynor's excellent multi-database support is bundled into trunk, Django does not support multiple databases.

At the same time, the structure of Django sites may be of interest to you . Without additional information about your intentions, it is difficult to give the best advice.

+4
source

, Django. , .

SaaS, " " , , Django.

, : Django.

+1

There is an open source project that claims to handle a large amount of infrastructure for the base site with the 37Signals showroom: http://github.com/saas-kit/django-saas-kit p>

0
source

Source: https://habr.com/ru/post/1720241/

More articles:


All Articles