-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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: add Azion as a deployment option #10481
base: main
Are you sure you want to change the base?
Conversation
Hi @VitorAEltz! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
✅ [V2]Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
⚡️ Lighthouse report for the deploy preview of this PR
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
I assumed this is spam but turned out it's not. However, as said in the deployment doc, we don't accept anything bigger than a single paragraph that points to your own deployment documentation. |
Perfect Josh, I will make the change, thanks |
@slorber Just so we are on the same page: are we still open to such promotional contributions? I would personally vote no but we haven't historically rejected anyone. |
I would also vote no. I postponed my review of this PR because I also think we can't continue growing our deployment page this way, nor want to arbitrate if a provider deserves to be added to the page. The goal of this page is not to list every possible deployment option and even less to provide marketing and easy-to-obtain backlinks to said services. I was thinking that in the future we could limit this page to just a few handpicked deployment platforms that we know and are willing to document more extensively (GitHub Pages, Netlify, Vercel), and move everything else to a community-driven resource of other third-party options (it could be as simple as a GitHub discussion) |
That sounds like a good idea:) |
#Pull Request Title: feat-add-azion-deployment
##Description:
This pull request adds documentation for deploying a Docusaurus site to Azion. The new section provides detailed steps for three deployment methods: starting from a template, importing from GitHub, and using the Azion CLI.
Changes:
File: website/docs/deployment.mdx
Summary of Changes:
Added a new section titled "Deploying to Azion".
Included detailed instructions for:
Starting from a template in the Azion Console.
Importing a project from GitHub.
Deploying using the Azion CLI.
Pre-flight checklist
Motivation
Test Plan
Test links
Deploy preview: https://deploy-preview-10481--docusaurus-2.netlify.app/