-
-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app file structure #100
Comments
Hi @summer88,
The location you where you call a tasks is depend on where you want the task to go to the background. |
Django Q does not enforce a location for your task. It can be any function inside your environment. You can use imports: from my_app import somefunction
async(somefunction, somearguments) or full paths: async('my_app.somefunction', somearguments) both do the same thing. |
Thanks for the explanation, I will try it out asap! |
I've already worked with django, sorry if this is a silly question.
This is the usual file structure:
project:
mydata_app
manage.py
I should add the tasks to a file called tasks.py?
It should be inside mydata_app or in the projects directory?
the call for the tasks can be placed in the views.py?
The text was updated successfully, but these errors were encountered: