Yeah, I just made it work. Since I used Apache2 to host web2py in EC2 instance, after updating the scheduler.py file, I need to restart the Apache2 server by: sudo service apache2 restart
and then restart the web2py-scheduler by: sudo stop web2py-scheduler sudo start web2py-scheduler (this is assuming the "/etc/init/web2py-shceduler.conf" is there) Thanks! On Friday, December 19, 2014 3:20:35 PM UTC-5, Niphlod wrote: > > > >> In my real-word application, I used MySQL database from AWS RDS. Do you >> think if it will also cause "concurrent" issue? >> > > nope, mysql is fine with concurrency > > >> >> I see in the gist that only the gluon/scheduler.py file has been changed. >> So is it fine if I only update this scheduler.py file from your new commit? >> I tried to update this python file and it seems the worker assignment >> didn't change for the toy application. Do I need to restart the web2py >> application to make it work? How I can do that if it is already deployed in >> EC2 instance? >> >> you can just pull in the scheduler.py file with the modifications: > there's no breaking changes in the modification I did (or use this > <https://raw.githubusercontent.com/niphlod/web2py/scheduler/enhancement/gluon/scheduler.py>). > > you just need to restart the scheduler to make the changes work. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
