Monday, 23 April 2012< ^ >
arjan has set the subject to: Zotonic - the Erlang CMS
Room title: "Zotonic"
Allow users to change subject
Allow users to send private messages
Allow users to query other users
Allow users to send invites
Make room semianonymous
Default users as participants
Make room members-only
Make room moderated
Make room password protected
Make room persistent
Make room public searchable
Make participants list public
[07:17:05] maas.maarten.zeeman joins the room
[08:03:55] maas.maarten.zeeman leaves the room
[09:23:23] arjan joins the room
[10:07:58] maas.maarten.zeeman joins the room
[11:00:26] maas.maarten.zeeman leaves the room
[11:26:14] arjan leaves the room
[11:27:09] arjan joins the room
[12:13:31] maas.maarten.zeeman joins the room
[16:17:40] fl joins the room
[16:20:25] <fl> I'm looking into Zotonic and have a question about working with multiple sites.
[16:21:05] <fl> I've read that Zotonic can be used either with different databases or using different schemas.
[16:21:49] <fl> Since I prefer the schema approach (i.e. 1 db and a schema per user), I tried to set it up. This however failed.
[16:23:10] <fl> Note: when I said "schema per user", I implicitely also meant a user per site; each site would thus have its own user and schema
[16:23:33] <fl> Is this actually supposed to work?
[16:29:04] <arjan> I'm not sure
[16:29:10] <arjan> I guess with postgresql you can set it up that way
[16:29:16] <arjan> schema's do have the concept of 'owners'
[16:29:32] <arjan> so if you create each schema with the owner for the correct site, it should work
[16:29:49] <fl> Since it didn't work for me, I had a look in z_install.erl. Since that does not include the schema explicitely in the sql statements, I also had a look in pgsql_pool.erl which takes Host but only seems to include the necessary options only in case a new connection is to be allocated.
[16:31:12] <fl> about the 'owner' concept: indeed, when I tried it, I basically created a schema e.g. site1 and granted user1 everything on schema site1
[16:31:52] <fl> However, I noticed that the model was not created within the schema, which is why I started to look at the code creating the model.
[16:40:26] <fl> I wonder where our pool (as described in README-epgsql_pool) is created (I suppose it would have to be created based on the different site config files)
[17:25:23] maas.maarten.zeeman leaves the room
[18:27:25] arjan leaves the room
[18:36:38] maas.maarten.zeeman joins the room
[19:08:07] maas.maarten.zeeman leaves the room
[20:11:55] arjan joins the room
[20:14:48] arjan leaves the room
[20:15:55] arjan joins the room
[20:56:14] simon.smithies joins the room
[21:07:22] maas.maarten.zeeman joins the room
[21:26:36] maas.maarten.zeeman leaves the room
[21:33:20] simon.smithies leaves the room
[21:54:34] arjan leaves the room