Jonas Huber
Jonas Huber
@adelmemariani can you approve this?
> from memory: > > on production, in main folder, with activated virtualenv > > ```shell > git checkout master # or release/xxx > > pip install -r requirements.txt >...
Two new management commands that should alsoe be part of the release procedure: https://github.com/OpenEnergyPlatform/oeplatform/issues/1297
I have found another step that is missing in our current release procedure. We have introduced the [citation.cff](https://github.com/OpenEnergyPlatform/oeplatform/blob/bugfix-1270/store-agreed-oem-field-value-in-review-datamodel/CITATION.cff#L31) file, which also contains a version. This should be updated every time...
From now on for each release we have to run the command: ```bash python manage.py compress ```
I will work on the compression & template integration part. Also will have a look at the scss build.
As suggested by @holycrab13 we could use [DALICC](https://www.dalicc.net/). The databus also uses it https://dbpedia.gitbook.io/databus/model/metadata/version#id-2.-legal-provenance-and-attribution
https://api.dalicc.net/docs#/licenselibrary/get_license_by_id_licenselibrary_license__license_id__get
In this article you will find further suggestions and insights: https://forum.openmod.org/t/public-licensing-ontologies/2756 It states that some information found in DALICC may not be correct - not sure if this is relevant....
Before we do this, we need to import the oeo and oeo extended into the oekb. Then we have a "single source" where we can retrieve the oeo + extended...