Oh, Man, Massimo - this is great.... I'll look in a few mintues...
I'm thinking this is just the tip of a workflow thing - we should talk a bit... First: local repo is good (localhost); Second: deploy to remote server Third: commit to "project" or public place (e.g. bitbucket or google source, once that's available). Thanks for initiating this! On Tue, Apr 28, 2009 at 11:40 PM, mdipierro <[email protected]> wrote: > > there is a new experimental feature in trunk. > > run from source > easy_install mercurial > > go to web2py admin and design an app > > you will notice a new menu item [mercurial] > > if you click on it it creates new mercurial repo associated to the > app. > if you write a comment and "commit" the current app gets committed in > the repo. > > This needs to be polished. we should add buttons to revers, get curret > status etc. > > I could use some help... anybody? > > I am using these APIs > > > http://www.selenic.com/mercurial/wiki/index.cgi/MercurialApi#head-fee0fb0aca31913079ee91bccde7bbd9b2a88215 > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
