The SSP website is generated from a git repository and published through github.io. The most up-to-date repository is likely to be Uninett's internal gitlab. A script is used to generate the website.
For every release the website is updated. So, in order for the SSP community to assume responsibility for the release process, we need to be able to update the website.
Having the cronjob that generates the website is a good first step. It'll enable us to generate the website.
2nd step: for Niels to find a place to run the script and test it
3rd step: ensure website content in SSP on Github is synced with the content in Uninett's gitlab
meijer
commented
3 years ago
The SSP website is generated from a git repository and published through github.io. The most up-to-date repository is likely to be Uninett's internal gitlab. A script is used to generate the website.
For every release the website is updated. So, in order for the SSP community to assume responsibility for the release process, we need to be able to update the website.
Having the cronjob that generates the website is a good first step. It'll enable us to generate the website.
2nd step: for Niels to find a place to run the script and test it 3rd step: ensure website content in SSP on Github is synced with the content in Uninett's gitlab