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

Staging environment #4469

Closed
collabnix opened this issue Mar 19, 2021 · 1 comment
Closed

Staging environment #4469

collabnix opened this issue Mar 19, 2021 · 1 comment
Labels
closed: question This issue is a user error/misunderstanding.

Comments

@collabnix
Copy link

I have a developer website based on docusaurus. Would like to know what general practice do people follow for staging and production environment . Before pushing my changes to prod site, I want to showcase it to my management. Do suggest.

@collabnix collabnix added status: needs triage This issue has not been triaged by maintainers closed: question This issue is a user error/misunderstanding. labels Mar 19, 2021
@slorber
Copy link
Collaborator

slorber commented Mar 19, 2021

Hi, please remember issues are not for questions.

If you use a modern Jamstack / static hosting solution like Netlify or Vercel, each PR against master will have a "deploy preview" enabling you to review the changes online with a unique URL. Once you merge the PR to master, it will automatically deploy to production. This is the workflow I would recommend.

See for example #4409 (comment)

image

It is also possible to set up one deploy URL per git branch.

Github Pages can only have a single URL per repo so it is not a good fit.

If you want to use a single git branch or don't want a modern Jamstack hosting solution, you'll have to figure out yourself how to host the staging site. There are thousands of way to host static files, using docusaurus serve, Apache, Nginx, Varnish...

@slorber slorber closed this as completed Mar 19, 2021
@Josh-Cena Josh-Cena removed the status: needs triage This issue has not been triaged by maintainers label Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: question This issue is a user error/misunderstanding.
Projects
None yet
Development

No branches or pull requests

3 participants