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 a member of Aiki
Framework Developers, 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-devel
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework-devel
More help   : https://help.launchpad.net/ListHelp

Reply via email to