Trying to run following script inside a controller:
python web2py.py -S myapp -M -N -R applications/myapp/private/alerts.py -A
1 2 3
and getting:
SyntaxError: invalid syntax at web2p*y*.py
Can someone assist please.
Thanks & Regards
AT
--
---
You received this message because you are sub
I've just realized that this script is supposed to be run outside the
web2py application and it would work as if it was inside the application
controller, am I right?
Is there any way to invoke a controller function or webservice
asynchroously, from another controller function?
Thanks
On Wed
Source distribution:
>From the main web2py folder
python web2py.py -S app -M -N -R path/to/myscript.py -A a b c
Binary distribution (windows):
web2py.exe -S app -M -N -R path/to/myscript.py -A a b c
myscript.py can be anywhere as long as path/to is its absolute path or
relative path from the p
Hi,
Here when i run the above command , it says 'application could not be
found'. But, i double checked , that folder is there and also it appears
when I run the admin interface. Are there any naming conventions that for
which I have to take care about?
Thanks,
Harsh Mehta
On Saturday, 30 Jun
On Friday, February 24, 2017 at 8:50:56 AM UTC-8, klas@gmail.com wrote:
>
> Dear community,
>
> I am working on a school project, using web2py. I have a Python script,
> that should be run in background, because it takes several minutes.
>
> First, I tried using Homemade Task Queues, because t
On Friday, February 24, 2017 at 11:51:58 AM UTC-8, Dave S wrote:
>
> On Friday, February 24, 2017 at 8:50:56 AM UTC-8, klas@gmail.com
> wrote:
>>
>> Dear community,
>>
>> I am working on a school project, using web2py. I have a Python script,
>> that should be run in background, because it
On Friday, February 24, 2017 at 11:50:56 AM UTC-5, klas.eq...@gmail.com
wrote:
>
> Dear community,
>
> I am working on a school project, using web2py. I have a Python script,
> that should be run in background, because it takes several minutes.
>
> First, I tried using Homemade Task Queues, becau
Thank you for your answers.
But still: What about the second point? Running the shell to start the
background script is a process that never ends, thus systemd stays in
"activating" state, because the action is never finished. And I guess it's
not a good practice for a daemon to keep starting b
On Monday, February 27, 2017 at 5:13:51 PM UTC-5, klas.eq...@gmail.com
wrote:
>
> Thank you for your answers.
>
> But still: What about the second point? Running the shell to start the
> background script is a process that never ends, thus systemd stays in
> "activating" state, because the actio
I just found the solution: just create another systemd service for the
background task. Before I was using ExecStartPost= in the web2py-service,
which created timeouts. Now it works perfectly.
Anyway, thank you for your effort
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documen
10 matches
Mail list logo
