Welcome to Geeklog, Anonymous Saturday, December 21 2024 @ 10:24 pm EST
Geeklog Forums
Multiple Geeklogs with shared code?
Status: offline
jmatt
Forum User
Junior
Registered: 01/06/03
Posts: 30
Location:Tatertown, KY, USA
I've been playing with the thought of running multiple Geeklogs on a single server, and wondering if it could be done without installing multiple copies of the Geeklog code.
Having all the config stuff in the database in 1.5 helps. I'd start with some scheme for mapping the URLs for each Geeklog to a unique pair of siteconfig.phg and db-config.php, which would point to a unique database for each site. But it might get a little trickier than that.
The default setup has a mixture of site-independent stuff ("code" and site-dependent stuff ("data", logs, etc) in /path/to/geeklog. I haven't looked at all the path settings in the config db yet to see how easy it would be for multiple sites to point to a single directory (or set of directories) for site-independent stuff, and unique directories for stuff that varies between sites.
At this point, this is mostly an academic question for me. I don't really have a need for multiple sites right now. And if I do, the amount of disk space wasted by the simple technique of just replicating everything might not be big enough to worry about. But I'm a geek, and sometimes I like to waste a lot of time trying to do things the "right" way instead of the easy way, and it seems right to avoid duplication of code.
Has anybody tried this, or thought about it enough to have any thoughts on whether it's a reasonable idea?
Having all the config stuff in the database in 1.5 helps. I'd start with some scheme for mapping the URLs for each Geeklog to a unique pair of siteconfig.phg and db-config.php, which would point to a unique database for each site. But it might get a little trickier than that.
The default setup has a mixture of site-independent stuff ("code" and site-dependent stuff ("data", logs, etc) in /path/to/geeklog. I haven't looked at all the path settings in the config db yet to see how easy it would be for multiple sites to point to a single directory (or set of directories) for site-independent stuff, and unique directories for stuff that varies between sites.
At this point, this is mostly an academic question for me. I don't really have a need for multiple sites right now. And if I do, the amount of disk space wasted by the simple technique of just replicating everything might not be big enough to worry about. But I'm a geek, and sometimes I like to waste a lot of time trying to do things the "right" way instead of the easy way, and it seems right to avoid duplication of code.
Has anybody tried this, or thought about it enough to have any thoughts on whether it's a reasonable idea?
9
12
Quote
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
See this recent discussion. Slightly different focus, but contains links that should help you.
bye, Dirk
bye, Dirk
10
14
Quote
All times are EST. The time is now 10:24 pm.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content