Hi Djangonauts,
I am developing a Django project (with a few pluggable apps).
I want to offer this project as a SaaS (something like 37signals.com).
i.e: customer1.product1.com , customer2.product2.com etc
product1 could be the basecamp product2 could be highrise and so on.
I want to know
Savy kirjoitti:
>
>
> Hi Djangonauts,
>
> I am developing a Django project (with a few pluggable apps).
>
> I want to offer this project as a SaaS (something like 37signals.com).
>
> i.e: customer1.product1.com , customer2.product2.com etc
>
> product1 could be the basecamp product2 could b
There is also second issue to consider - single database
is a potential security threat (one customer might be able to access
data of second customer if you have a bug in your code).
--
Tomasz Zielinski,
http://pyconsultant.eu
--~--~-~--~~~---~--~~
You received t
: Django SAAS projects
Hi Djangonauts,
I am developing a Django project (with a few pluggable apps).
I want to offer this project as a SaaS (something like 37signals.com).
i.e: customer1.product1.com , customer2.product2.com etc
product1 could be the basecamp product2 could be highrise and so on
On Oct 16, 7:09 pm, Savy wrote:
> Hi Djangonauts,
>
> I am developing a Django project (with a few pluggable apps).
>
> I want to offer this project as a SaaS (something like 37signals.com).
>
> i.e: customer1.product1.com , customer2.product2.com etc
>
> product1 could be the basecamp product2
Hi
I developed a django based SAAS project and im very happy with it
I have a single main project and differents 'branches' for each
customer. We use git to manage the workflow and a github account which
helps a lot for centralisation.
Customers versions are juste differents settings with diffe
6 matches
Mail list logo