[Flow] How to build a SaaS Service?

[Aimo Kuenkel]

Hi Axel,

This is exactly what we're doing here: once instance, accessible through wildcard subdomain and with a "subdomain" field for a customer.
I could help you i think, but could you explain why you want to create a new database for each new customer?
I don't think this is what you really want.

Greetings,

Aimo

-----Ursprüngliche Nachricht-----
Von: flow-bounces at lists.typo3.org [mailto:flow-bounces at lists.typo3.org] Im Auftrag von Axel Wüstemann
Gesendet: Samstag, 22. Februar 2014 10:40
An: TYPO3 Flow mailing list
Betreff: [Flow] How to build a SaaS Service?

Hello,

I would like to have some ideas, hwo I could build a SaaS solution:
- one Flow instance
- multiple databases, one for each account
- each account should have its own subdomain.

This are my thinkings until now:

Beside the databases for each account there should be additional an overall database which holds all accounts. I should create a package for the account management which is able to create a subdomain (no idea how to do so) and create the individual database for this acccount.

All further account stuff - authentification, more users per account then will be treated via the indicidual instance of the application (subdoman.example.com).

I would appreciate any further ideas to this topic.

Thanks
Axel
_______________________________________________
Flow mailing list
Flow at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/flow