Ok, think we have a good strategy on how to keep these separate at the
moment. Also, need to not require aiki to write to so many locations.
Closing as wontfix right now
** Changed in: aikiframework
Status: Triaged => Won't Fix
--
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:
Won't Fix
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
