Ok, fosdevel, cxadams and I just had a really great discussion about what the aiki updater should look like, and realized we needed to clarify some boundaries in the system design.
Right now the admin interface uses aiki to make itself, and then aiki devs use this to make AikiSites. However, the distinction between the admin interface and site created is not clear in the design of aiki and the layout on the filesystem. But, what we realizes is that Aiki must get simpler. We need to simplify and clarify it. So, we realized that the admin interface and the design of the /assets folder needs to be resolved. What does make sense is that the admin inteface is an AikiApp in its own right, so we should move it to its own folder /admin. This means that an aiki installation should be able to run even without it. However, there should be very strict separation by defaul between /admin and the other AikiApps. So if we like this line of thinking, then we need to think of a way to create the first aiki app when first starting/using/installing aiki, and this also opens the path to implement the idea that an aiki site can have multiple apps/site. I hope this all makes sense. I updated the three main blueprints this is about and tried to tie them together. Any help refining this idea and prioritizing our next steps is important, as we have to take this process step at a time and not get too overwhelmed. The key to future aiki success is simplicity. So, the update system fosdevel is outlining, and is influencing/influenced by our discussions, but can proceed: http://aikiframework.org/wiki/Aiki_Robust_Update_System The next thing we can do is clarify this spec, which is essentially defining what an AikiApp (AikiSite) is? What is inside this folder, and for now, a default app. Custom it could be called, or just stick with /assets for now. Eventually would be good to get to a place where this is user defined at installation or inside aiki: https://blueprints.launchpad.net/aikiframework/+spec/custom-directory Next would be to make AikiApps real meaning need a way to install/remove aiki apps and solve conflicts between them. We can save making an AikiApp store for later: https://blueprints.launchpad.net/aikiframework/+spec/make-aikiapps And finally, that allows for finalizing some default admin interface issues: https://blueprints.launchpad.net/aikiframework/+spec/refined-default-admin-installation Ok, apologies, this is some very round thinking, but still important to decide and plan out. Any thoughts on what I've written? Jon -- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : aikiframework-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
