Skip to content
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

How do we deploy the documentation? #231

Closed
Cube707 opened this issue Aug 12, 2022 · 3 comments · Fixed by #412
Closed

How do we deploy the documentation? #231

Cube707 opened this issue Aug 12, 2022 · 3 comments · Fixed by #412
Labels
ci Continuous Integration documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@Cube707
Copy link
Collaborator

Cube707 commented Aug 12, 2022

@magmax

How do we currently delpoy the documentation? .github/workflows/documentation.yml only creates a zip-file and attatches it to the action, so are you currently manually deploying it?

Should we create an automated process for that, so that changes will be autouploaded to the webserver?

@Cube707 Cube707 added help wanted Extra attention is needed ci Continuous Integration documentation Improvements or additions to documentation labels Aug 12, 2022
@staticdev
Copy link
Collaborator

staticdev commented Aug 12, 2022

@Cube707
Copy link
Collaborator Author

Cube707 commented Aug 12, 2022

yes, but we are currently using magmax's webserver under magmax.org/python-inquirer/, so the question is if we want to keep it there, if we want to autodeploy to that server, or if we want to switch to readthedocs

@Cube707
Copy link
Collaborator Author

Cube707 commented Aug 30, 2023

deploying to read-the docs in the future

@Cube707 Cube707 closed this as completed Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous Integration documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants