start processes separately: you can't launch daemon processe within a
web2py action, for pete's sake :P
web2py.py -a yourpassword #<--the webserver
web2py.py -K yourappname#<-- the scheduler
gluon/contrib/websocket_messaging.py -k yourkey -p 8888 #<-- message
dispatcher
On Wednesday, April 1, 2015 at 5:19:42 AM UTC+2, Carlos Costa wrote:
>
> I would like to use scheduler with a task sends websocket messages but it
> looks like they conflict with each other.
> I am able to run only one of them.
>
> If I start scheduler first, websocket freezes web2py.
> If I start websocket first scheduler do not run any worker.
>
> I start we2py with web2py.py -K app -a password -X -D15
>
> In some action I do this to start the websocket
>
> import subprocess
> subprocess.call("python gluon/contrib/websocket_messaging.py -k mykey -p
> 8888".split(' '))
>
> but this freezes everything.
>
> If I start websocket from shell manually both things work but I would like
> my app to guarantee that things are running.
>
> Some idea why this is not possible?
>
> Running 2.9.12 with python 2.7 on Ubuntu 14.10
>
--
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.
