I agree completely. The multi-db suport should help, but need to expose in the interface.
And, versioning needs to be default on aiki sites. Jon On Sun, Mar 20, 2011 at 10:40 PM, Christopher Adams <ch...@raysend.com> wrote: > This is really necessary though! > > Although Aiki saves the revision history, what it is missing is the > control! > > There is no analogy in Aiki of doing a pull request, but there needs to > be. > > For example, if I am the Admin for OFLB, let's say we have the live site > running at OFLB.org that only I can push changes to. (Since we shouldn't > be giving the ability to deploy to every OFLB developer.) > > In addition, we have a test server running at test.OFLB.org. Developers > should be able to hack on that, or even better "clone" the site and hack > on their own instance of it. > > When the developer commits a fix, he should be able to make a pull > request. I can then review his changes and push them to the live site > after testing. As the Admin I should have fine granular control about > which commits to push to the live site. > > As it currently stands, developers have the power to hack on a live site > (very dangerous), or, if they only have access to a test site, the Admin > has a very hard time pushing selective changes to the live site (it > would have to be done by hand). > > Perhaps it would be possible to achieve this by putting the controller > widgets in a flat .sql file, which you can hack on in a text editor > (although it's a bit easier to break a .sql file if you don't have the > syntax right) and then import that back into a database. > > -- > You received this bug notification because you are subscribed to > aikiframework. > https://bugs.launchpad.net/bugs/718732 > > Title: > synchronise to external versioning > -- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/718732 Title: synchronise to external versioning Status in Aiki Framework: Opinion Bug description: In https://bugs.launchpad.net/openfontlibrary/+bug/718522 I understand Aiki stores revisions of its controllers in its database. Now having the controllers in the database is a win, because it allows easier editing access. However, many programmers like to work in their favourite text editor. Also, a database is a brittle centralised technology. Therefore I would request Aiki to synchronize its database with revisions to a git repository. This allows for easy redundant backups, increases data portability, and makes it more attractive for people who already have coding experience to join Aiki projects. Maintainers can grant access to the git repository in the way which they think is appropriate—this doesn’t need to be handled by Aiki. _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : aikiframework.admins@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
