-
Notifications
You must be signed in to change notification settings - Fork 84
Add hosting config file(s) to project scaffolding #234
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
Labels
Comments
If we could detect when these CORS errors happen, maybe we should show huge error modal on the UI? |
RonithManikonda
added a commit
that referenced
this issue
Nov 7, 2024
add configuration files for Vercel, Netlify, and Cloudflare Pages to simplify deployment and address CORS header issues in TutorialKit. This improves the setup experience by automating build commands and headers for common hosting providers, reducing manual configuration steps. close #234
RonithManikonda
added a commit
that referenced
this issue
Dec 19, 2024
moved the `generateHostingConfig` function to a new file with improved imports for hosting provider configuration files (`vercel.json`, `netlify.toml`, `_headers`). updated the function to work with the new imports and streamlined configuration generation. this change reduces clutter in the main implementation file and improves modularity by isolating hosting-related logic. closes #234
RonithManikonda
added a commit
that referenced
this issue
Jan 9, 2025
Adjusted the project scaffolding wizard to allow users to select only one hosting provider at a time, laying the groundwork for improved deployment configuration. Related to #234
RonithManikonda
added a commit
that referenced
this issue
Feb 27, 2025
RonithManikonda
added a commit
that referenced
this issue
Mar 5, 2025
Fixes Prettier errors to pass tests and ensure consistent code style. close #234
RonithManikonda
added a commit
that referenced
this issue
Mar 12, 2025
RonithManikonda
added a commit
that referenced
this issue
Mar 13, 2025
RonithManikonda
added a commit
that referenced
this issue
Mar 19, 2025
RonithManikonda
added a commit
that referenced
this issue
Mar 19, 2025
RonithManikonda
added a commit
that referenced
this issue
Mar 19, 2025
Fixed by #440. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
Because of CORS headers, deploying TutorialKit requires additional settings for each hosting provider.
Although we document that in https://tutorialkit.dev/guides/deployment/, not everyone reads the manual;) and I've heard feedback from users who'd tripped over the deployment story because of that.
Describe the solution you'd like.
With configuration files dedicated to the most common hosting providers, we can remove friction from deploying a tutorial project, so that aspects like setting up the build command or or headers is automatically taken care of.
Additionally, having this as a step in the wizard will highlight to a user the deployment capability itself.
Describe alternatives you've considered.
We could configure all the "usual suspects" automatically, but making it an additional step in the wizard might be a better option as it will reduce the unnecessary files generated.
Additional context
We can start with Vercel, Netlify and Cloudflare Pages to cover the range we have in our docs: https://tutorialkit.dev/guides/deployment/
The text was updated successfully, but these errors were encountered: