Where Should I Place The One-time Operation Operation In The Django Framework?

I want to perform some one-time operations such as to start a background thread and populate a cache every 30 minutes as initialize action when the Django server is started, so it

Solution 1:

I just create standalone scripts and schedule them with cron. Admittedly it's a bit low-tech, but It Just Works. Just place this at the top of a script in your projects top-level directory and call as needed.

#!/usr/bin/env pythonfrom django.core.management import setup_environ
import settings
setup_environ(settings)
from django.db import transaction

# random interesting things# If you change the database, make sure you use this next line
transaction.commit_unless_managed()

Solution 2:

We put one-time startup scripts in the top-level urls.py. This is often where your admin bindings go -- they're one-time startup, also.

Some folks like to put these things in settings.py but that seems to conflate settings (which don't do much) with the rest of the site's code (which does stuff).

Solution 3:

For one operation in startserver, you can use customs commands or if you want a periodic task or a queue of taske you can use celery

Solution 4:

__init__.py will be called every time the app is imported. So if you're using mod_wsgi with Apache for instance with the prefork method, then every new process created is effectively 'starting' the project thus importing __init__.py. It sounds like your best method would be to create a new management command, and then cron that up to run every so often if that's an option. Either that, or run that management command before starting the server. You could write up a quick script that runs that management command and then starts the server for instance.