bitkarrot / scheduler Goto Github PK

unfortunately I get this error when I hit install, tried also with 0.1.0 same error.

no further informations available, can you help out and point into right direction?

lnbits 0.12.4 running on citadel node

• fix the javascript

add an option to run a local python script if a single Rest API call is insufficient for application

• Set Environment Variables on front end UI, connect to cron_handler

• Add option in cron_handler to remove environment variables.

• these are global environment variables.

• Individual job env variables do not exist yet, this would be a future feature.

• add LNBits API end point selection to command sector
• directions TBD from vlad

• each time a cron job is triggered it should invoke one action
• the action is a REST HTTP call
  • please see below some screens from Postman
  • we can have something similar
  • the example below calls an API that updates a certain extension to the latest version
    • the API does not exist yet, is for demo purposes only
• we should not add support for OS wise actions (like rmdir) for now (keep it simple(r))
• the result of the job execution should be saved in a table (HTTP success status and response body if any)
  • this way the user can check that the action was executed at the correct time with the correct params

Call Config:

Call Body

• refreshing page changes the job status of jobs running.
• need to fix this so that it doesn't reset the job status

• Add validation checks on frontend js for crontab string
• add shortcuts for hourly, daily etc crontab formats.

rename from crontabs to scheduler in all files.

• Add option for multiple http requests with results chained together

• Add crontab loggin on backend
• Add crontab logging visibility on front end

• clean up naming artifacts and unused methods from user manager ext which was the template for this repo originally
• refactor any relevant parts.

Thoughts:

All the cron tabs which will be executed save you time and give you more power. Its a little bit like changing the settings.
The logo clarifies something else on the first view.

Improvment:

Something like that

Convert this test file to a proper pytest unit test

https://github.com/bitkarrot/scheduler/blob/main/tests/cron_handler_test.py

get rid of {%raw%} similar to what is discussed here

https://github.com/lnbits/lnbits/pull/2130/files