[Ur] Multitenancy

[Simon Van Casteren]

In general, not really. And at the moment I don't have time to implement
the automation so I for sure will do it manually. But I plan to add a
"Demo" button where people can check out the whole application with some
demo data and can do whatever they want. I wanted to implement that also as
a seperate tenant, and after a few days of inactivity delete those "demo
tenants".

Secondly, as a client I would appreciate it if I could buy this product and
immediately get my environment up and running, so not having to wait
minutes-hours until I can start using what I bought. This is not that
important right now, but I would like to have the possibility.

2018-05-13 20:11 GMT+02:00 Adam Chlipala <adamc at csail.mit.edu>:

> I'm confused about something: do you really expect to add new tenants
> frequently enough that it would be a problem for you to have to log into
> the server and run a shell script each time?  Would it even be a problem if
> you had to edit configuration files manually on the server each time?
>
> On 05/13/2018 02:02 PM, Simon Van Casteren wrote:
>
>> As I see it now, I'll probably have an API endpoint "new_tenant" that
>> will run the following:
>>
>> * Run a shell script to set up a new DB and load default data.
>> * Write the necessary config for a new fastCGI server with the new
>> connection string into my nginx config and reload nginx, as I've read this
>> should not impact the other servers. I'll probably add some notification to
>> myself whenever I do this so I don't silently start thousands of servers
>> when something goes wrong.
>>
>
> _______________________________________________
> Ur mailing list
> Ur at impredicative.com
> http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.impredicative.com/pipermail/ur/attachments/20180513/5b6201ba/attachment-0001.html>