-
Notifications
You must be signed in to change notification settings - Fork 22
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
upgrade staging to latest stable release #101
Comments
@boney-bun please do this deploy staging onto geonode.kartoza.com, keeping all the content on that server. Configure it to accept staging.geonode.kartoza.com as well. Then we will close down the old staging server |
Also configure it to accept geosafe.kartoza.com And it must have the generic theme (not INGC) staging.geonode.kartoza.com DNS is now pointing to the geonode.kartoza.com host (from today) |
@lucernae please complete this before the Hetzner switch next week. cc @AndreLester To summarise:
|
I've cancelled the VPS instance, please do the above still |
GeoNode 2.8
stable GeoSAFE
stable QGIS server etc.
ensure the documentation and Rancher catalog is clear to follow for doing a staging release
then deploy to production on geonode.kartoza.com when approved.
The text was updated successfully, but these errors were encountered: