The problem here is that most version control systems need a folder,
and we really don't want aiki files in our repo to get near custom
Is custom really good? The url is: http://SOMESITE/custom
rather it be something like http://SOMESITE/srv or
http://SOMESITE/home to mirror linux
could even make it http://SOMESITE/home/SITENAME to show we supporting
idea that one aiki installation can support multiple hierarchies.
On Fri, Dec 24, 2010 at 3:32 PM, Bassel Safadi <email address hidden> wrote:
> I think we add /custom and keep the current structure so /assets is for our default assets..
> btw the whole idea of having assets folder is that it's not really necessary for aiki functionality, one can remove it and and keep aiki working without the admin panel, if custom solution is needed.
> You received this bug notification because you are a direct subscriber
> of the bug.
> assets contains user files and core files
chat/skype: kidproto | irc: rejon