-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Assets: implement migration for old uploaded files #12326
Comments
@etj I guess that keeping the old files inside the previous location won't break GeoNode and Geoserer, right? |
@giohappy
|
12 tasks
12 tasks
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Continuation of #12124
Some old installations have the uploaded data into
/data
.The recent importer stores the uploaded data into
.../STATIC_ROOT/uploaded
, and GeoServer publishes the geotiff from that directoryThe final migration to Assets will store the files in
.../STATIC_ROOT/assets
, and GeoServer shall publish the files from there.In order to clean up such obsolete setups, a migration script could be done that:
uploaded/
toassets/
(first checks if all the files are intouploaded/
)LocalAsset.location
fieldSuch a migration script should only be run by hand since we do not know if such files are also used for other purposes outside GeoNode, so the admin can choose to run it or not.
The text was updated successfully, but these errors were encountered: