Change to Upgrading Instructions #86

Closed
opened 2025-12-29 15:32:11 +01:00 by adam · 1 comment
Owner

Originally created by @dberube1 on GitHub (Jun 29, 2016).

I think that in the upgrading section of getting-started.md having users do a pip install -r requirements.txt before the manage.py steps would be beneficial. This would insure that all requirements are installed and updated to required versions.

Originally created by @dberube1 on GitHub (Jun 29, 2016). I think that in the upgrading section of getting-started.md having users do a pip install -r requirements.txt before the manage.py steps would be beneficial. This would insure that all requirements are installed and updated to required versions.
adam closed this issue 2025-12-29 15:32:11 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jun 29, 2016):

Just addressed this in fc5495e by introducing upgrade.sh which takes care of the housekeeping necessary to run a new release.

@jeremystretch commented on GitHub (Jun 29, 2016): Just addressed this in fc5495e by introducing `upgrade.sh` which takes care of the housekeeping necessary to run a new release.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#86