On Jul 8, 2009, at 4:29 PM, AchipA wrote: > > Err, are you saying @reboot did not work for you ?
I wrote that before I read your suggestion. I'm sure it would work for me, but sadly my ISP won't allow a long- running process like web2py. > I though it's > enough to do > > crontab -e > > and enter something like > > @reboot username cd /home/web2py && python web2py.py -i > 192.168.0.200 - > p 8000 -a 'recycle' > > (obvioudly you still have to start web2py manually the first time you > install it, but it should wake up just fine afterwards). > > On Jul 8, 9:24 pm, Jonathan Lundell <[email protected]> wrote: >> On Jul 8, 2009, at 11:44 AM, mdipierro wrote: >> >> >> >>> and what was a Jonathan talking about? >> >> Linux cron (or in my case FreeBSD cron, which amounts to the same >> thing). The idea is to get web2py running from a login account >> after a >> reboot, when presumably web2py cron isn't going to be of any help. >> >> I have things running. I'll post a brief recipe to this list shortly. >> >> >> >>> On Jul 8, 1:21 pm, NetAdmin <[email protected]> wrote: >>>> I'm talking about the cron from Linux. >> >>>> Sterling >> >>>> On Jul 8, 12:51 pm, mdipierro <[email protected]> wrote: >> >>>>> you talking about web2py cron or unix cron? >> >>>>> On Jul 8, 12:07 pm, AchipA <[email protected]> wrote: >> >>>>>> Actually, cron has a keyword for that. Specify the time of the >>>>>> task as >>>>>> @reboot and itt will be run only once, right after booting. >> >>>>>> On Jul 8, 4:47 pm, Mr admin <[email protected]> wrote: >> >>>>>>> You can use CRON entry like this to try and run web2py every 15 >>>>>>> minuses >> >>>>>>> # cron entry to run web2py every 15 minutes >>>>>>> 0,15,30,45 * * * * /root/runweb2py.sh >> >>>>>>> Here are the contents of the shell script. >> >>>>>>> #!/bin/bash >>>>>>> # >>>>>>> # runweb2py.sh >>>>>>> # >>>>>>> cd /home/web2py >>>>>>> python web2py.py -i 192.168.0.200 -p 8000 -a MyPassWord >> >>>>>>> On Wed, Jul 8, 2009 at 9:15 AM, Jonathan Lundell >>>>>>> <[email protected]> wrote: >> >>>>>>>> On Jul 8, 2009, at 5:13 AM, Mr admin wrote: >> >>>>>>>>> One thing you can do is, login to the box using ssh, edit your >>>>>>>>> models, views and controllers without using the admin >>>>>>>>> interface at >>>>>>>>> all. >> >>>>>>>> I'm not particularly concerned about the admin interface; I'm >>>>>>>> happy to >>>>>>>> develop locally (OS X in my case) and deploy updates via ssh. >> >>>>>>>> On Jul 8, 2009, at 5:21 AM, NetAdmin wrote: >> >>>>>>>>> As for running after a reboot, you could use cron to try and >>>>>>>>> start >>>>>>>>> web2py hourly. If it's running, it should give an error >>>>>>>>> message >>>>>>>>> that says "Address already in use" >> >>>>>>>> I don't like that this would put me off the air for an hour (or >>>>>>>> whatever interval). On the other hand, reboots are rare, so >>>>>>>> maybe it's >>>>>>>> not such a problem. >> >>>>>>>> I was vaguely thinking along the lines of having a cgi script >>>>>>>> that >>>>>>>> would be invoked by a request to web2py if web2py weren't >>>>>>>> running. But >>>>>>>> I haven't really thought out the implications of that. >> >>>>>>>> There's another problem, that Apache runs as a global user on >>>>>>>> the >>>>>>>> host. I use a PHP-only wrapper script for a couple of >>>>>>>> applications, >>>>>>>> such as WordPress <http://pragmatos.net>. So perhaps a wrapped >>>>>>>> PHP >>>>>>>> script to do the startup? >> >>>>>>>> Regardless, it'd be nice to have a recipe or three for running >>>>>>>> web2py >>>>>>>> via login account. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
