WebDev/Deployments: Difference between revisions

m
no edit summary
(differentiated requirements for library files)
mNo edit summary
Line 9: Line 9:
==Using requirements for a deployment==
==Using requirements for a deployment==


For a deployed product (such as a website) specify its packages in requirements files. We recommend splitting the packages down into separate file for separate roles, for example: requirements/dev.text, requirements/prod.txt, and requirements/test.txt (those needed only for CI builds).
For a deployed product (such as a website) specify its packages in requirements files. We recommend splitting the packages down into separate file for separate roles, for example: requirements/dev.text, requirements/prod.txt (this is also used for staging), and requirements/test.txt (those needed only for CI builds).


All requirements should be pinned, e.g.:
All requirements should be pinned by version number, e.g.:


   foo==0.3
   foo==0.3
Line 36: Line 36:
==Internal package server==
==Internal package server==


When a package is to be used, it will be uploaded to the internal package server.
When a package is to be used, it must be uploaded to the internal package server.


Existing servers:  
Existing servers:  
Confirmed users
502

edits