-
Notifications
You must be signed in to change notification settings - Fork 58
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
[docs] Migrate docusaurus deployment from surge to gh-pages #127
Comments
Hey @codesankalp when the label changes to |
@Amulya-coder would you still like to work on this? |
@isabelcosta hello, me again, I would like to try and tackle this one 😁 |
@isabelcosta You can make this issue available to other contributors |
@Wizardlemon You can go ahead 👍 |
I've tried to test out deployment on my own branch, but I'm having some trouble setting up the appropriate secret key for deployment. I'll investigate it for a while longer, and I'll continue on with it tomorrow, but for now I'm putting up the PR so that the workflow file can be reviewed, maybe someone knows what needs to be done, or can give me some helpful advice. |
Update: I've managed to successfully deploy the documentation to https://wizardlemon.github.io/anitab-forms-backend/ using the workflow actions after updating the docusaurus config file. I've figured out the issues I had with secret keys, and the config file also needed to be updated. If there's any more assistance that's neccessary with this migration, or if documentation updated are necessary as well, I'm available 😁 |
I think this https://docusaurus.io/docs/deployment#deploying-to-github-pages will allow me to configure things correctly. But if you feel there is any documentation about this that is related specifically to this project, feel free to create it or create an issue for it ;) |
Is your feature request related to a problem? Please describe.
It will be better to have the docs on the github-pages.
Describe the solution you'd like
Deploy the docs on gh-pages.
Take reference from this: anitab-org/mentorship-backend@4cc78ae
The text was updated successfully, but these errors were encountered: