The basic outline of putting static files into production is simple: run the collectstatic command when static files change, then arrange for the collected static files directory (STATIC_ROOT) to be moved to the static file server and served.
Depending on STATICFILES_STORAGE, files may need to be moved to a new location manually or the post_process method of the Storage class might take care of that.
Of course, as with all deployment tasks, the devil's in the details. Every production setup will be a bit different, so you'll need to adapt the basic outline to fit your needs.
Following are a few common patterns that might help.
If you want to serve your static files from the same server that's already serving your site, the process may look something like:
Push your code up to the deployment server.
On the server, run
collectstaticto copy all the static files intoSTATIC_ROOT.Configure your web server...