I use the glory of only the best distributed version control system (mercurial)!
On my server I have a subdomain that services mercurial through SSH. I put my web2py application under version control I created a .hgignore that ignores ^databases/ ^sessions/ ^cache/ and ^uploads/ I deleted the already included .hg folder and ran my own hg init, then ran hg add . hg commit -m "commit message" hg push ssh://hg.thadeusb.com/root/path/to/hg/repo/ Yes, now I have a web2py application under client-server version control, named /home/thadeusb/Workspace/MyApp Ok so now on my server, I have a directory named web2py_projects, in this folder I run hg clone ssh://hg.thadeusb.com/root/path/to/hg/repo/ hg update Now on the folder that serves my wsgihandler.py, I include the latestest stable web2py, and in the applications directory, includes a simlink named 'init' to my web2py_projects/MyApp. Effectively making it the default. When I'm finished testing on my workstation, i push the changes, and then on the webserver I pull them. The admin interface is completely disabled, and I only alter and change code from my workstation, while my server stays happy when a stable version of my site. If I need an updated copy of the database, I just SFTP the databases folder over to my machine, so I can have a current copy of the data to test with. This works really really well, and makes deploying updates so easy, and secure! -Thadeus On Tue, Sep 22, 2009 at 12:29 PM, MikeEllis <michael.f.el...@gmail.com>wrote: > > The problem isn't getting to the admin interface. I didn't even get > that far. The ticket appears when I browse to the application URL. > > On Sep 22, 12:54 pm, Kuba Kucharski <kuba.kuchar...@gmail.com> wrote: > > You should look for admin on 127.0.0.1:8001 > > You have configured it this way. > > > > ;) > > > > On Sep 22, 2009 6:19 PM, "MikeEllis" <michael.f.el...@gmail.com> wrote: > > > > I'm seeing more or less the same problem but I haven't managed to get > > the 2-process solution to work yet. I'm trying to use the > > recommendation in version 2 of the manual: > > > > """ An easy way to setup a secure production environment on a server > > is to first stop web2py and then remove all the parameters *.py files > > from the web2py installation folder. Then start web2py without a > > password. This will completely disable admin and appadmin. """ > > > > So I started web2py with the following command line on my (remote) > > webserver: > > python2.5 web2py.py -i my_server_ip -p 8000 -a "" & > > > > So far so good. It started and gave the "no password, no admin > > interface" message. > > > > Then I followed the second part of the recipe: > > > > """Next, start a second Python instance accessible only from > > localhost:""" > > nohup python2.5 -p 8001 -i 127.0.0.1 -a '<ask>' & > > > > Second instance started with no complaints, but trying to reach the > > server from my laptop, e.g. > > > > http://my_server_ip:8000/init > > > > gives the "Admin is disabled because of insecure channel' ticket. Any > > idea what I'm doing wrong? > > > > Thanks, > > Mike > > > > On Jul 26, 1:09 pm, Randell <josephrandell.benavi...@gmail.com> wrote: > > On > > Mon, Jul 27, 2009 at 12... > > > > > <kuba.kuchar...@gmail.com>wrote: > > > > > > > Are you trying to access admin through localhost ?? > > Yes. > > > > > > > > Out of curiosity, w... > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
