not a bad idea, and also, this is consistent with roger's implementation of aiki sites, which allows one aiki installation to manage multiple sites...
so could have /aiki and then /site1 /site2 etc or /framework1 /framework2, etc Jon On Thu, Nov 17, 2011 at 3:29 PM, Christopher Adams <[email protected]> wrote: > Even better would be to separate the aiki core and the custom site into > separate folders in the root web directory. > > For example: > > /srv/www/example.com/public/aiki « contains aiki core code > /srv/www/example.com/public/framework « contains empty directory structure > for custom site > > Your webserver would likely point to > /srv/www/example.com/public/framework/index.php or something. The config > file would be in framework/, which would specify the path to the aiki/ > folder. Therefore, aiki could even be located at /usr/local/lib/aiki/. > Your copy of stable aiki/ could be in its own git repo. Your custom site > at framework/ could be stored in a separate repo. > > This is how Lithium does things: http://lithify.me/docs/manual/getting- > started/installation.wiki > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/694026 > > Title: > assets contains user files and core files > > To manage notifications about this bug go to: > https://bugs.launchpad.net/aikiframework/+bug/694026/+subscriptions > -- Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳ irc: rejon +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing) -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/694026 Title: assets contains user files and core files Status in Aiki Framework: Triaged Bug description: We need to decide on a file structure that is indepedent of site- specific assets like assets/extensions and other ones like assets/images which currently has default images in it. Also, there is custom javascript in the /assets/javascript folder. I think we should make a decision. Possibly, /assets is the place for default assets: /assets /apps /images /extensions /javascript /uploads Then need something like: /custom /apps /images /extensions /javascript /uploads And keep those completely empty on an installation. We should even keep these except for a README in each, and then remove /assets/uploads from the current trunk of aiki. Any other suggestions? The more I've been working with aiki, realize that its weird. The other thought is we could put something like: /assets /apps/default /images/default /extensions/default /javascript/default /uploads/default For the current default aiki assets for these folders. Thoughts? I think we should move on this sooner rather than later, noticing that several installations have a mix of core and custom assets. It just makes keeping the core VS custom distinction harder to make real...let's keep it real :) To manage notifications about this bug go to: https://bugs.launchpad.net/aikiframework/+bug/694026/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
