Closed TrueDoctor closed 4 years ago
As of now, I have integrated the documentation into the deployment process. I have a seperate webhook, that builds the current changes and publishes them to my website. (kobert.dev/ratatosk/[branch]{/doc}) But is currently down due to the renaming of the repo. You should have the rights to check the server configuration as well. It might be smarter to integrate it there
Doc now lives here -> Documentation
As we don't have a Jenkinsfile in our repo - do we need to do this in the jobset's configuration on the server? Or would it make more sense to somehow include this in the cargo build process (a.k.a. produce docs during the build by default and somehow deploy the docs from the CI somewhere on
kobert.dev
?)