The guide is suitable for production systems except for the context of proper security protocols (https, keeping your passwords secure, and any other site-specific rules your IT team has determined for your environment). Just to be clear: the documentation can not be aware of the specific security concerns of your own IT department (but makes the assumptions that there are some kind of concerns that you should be aware of).
I think the document could be clarified/made more precise by saying that from a security perspective: the document is not meant to illustrate production-oriented configuration, and you should take additional steps to ensure that when you install the software, you accomodate all IT concerns related to securing your environment.
All that being said, if you do take those additional steps in your production environment to ensure secure configuration, then you can follow the document to deploy to your production environment. That’s what we do at our own company. We don’t use docker, we build from the release and apply additional measures to ensure the application is secure (ie: we set up the SSL certs for HTTPS, we have protocols around database/service accounts, we grant specific permissions to specific accounts for accessing specific schemas, etc).