1. Remote file list (given a folder) and transfer (given a file name).
2. Results table:
- When a task is executed, it would be nice to have some sort of parameter like this:
store_results = None # Don't store results store_results = ['*.txt'] # Store as results all *.txt files store_results = ['filename1', 'filename2'] # Store as results files ( a result entry per file) store_results = ["*", "!*.nxs"] # All files except *.nxs
- 3. Examples with the password caching using something default in Django. Ideas:
SESSION_ENGINE = "django.contrib.sessions.backends.cache". It uses memory sessions (rather than the DB) for all sessions. The problem is when the memory runs out the sessions disappear..... The server would eventually purge the cache and make the user put on their passwords again...
Session data will be stored directly in your cache. However, session data may not be persistent: cached data can be evicted if the cache fills up or if the cache server is restarted.
Logmodel needs a flag to tag the log either as
5. Choose the interpreter in
submit_task. E.g. a parameter like
6. Minimize dependencies (Let's keep just celery and redis for now).
timeout. We have to see how to kill the process remotely and interrupt the celery task...
8. Ideas (not urgent!):
django-channelsto have a real update of the tasks. See example: https://github.com/VincentTide/django-channels-celery-example
django-celery-resultsto see in the admin the celery results tables.