-
Notifications
You must be signed in to change notification settings - Fork 313
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
Configure Gitpod for one-click quickstart #58
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Just a couple things.
Co-authored-by: Kent C. Dodds <[email protected]>
Co-authored-by: Kent C. Dodds <[email protected]>
Agreed, and I've adjusted the list to your recommendation. I've got a good batch of extensions I like working with, and I figured it was easier to remove the ones we don't want than to come up with the ones we do From @andrewbrey's comment remix-run/remix#2711
This was a great suggestion, and that's been implemented now too. A new user can spin up a workspace and immediately create an account with no Prisma errors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coolio 👍 Thanks for putting this together!
@jacobparis Would be lovely to have these in |
I will make that happen :) |
In this PR I've set up Gitpod with a custom Dockerfile that comes with Fly pre-installed. The goal is for people following the blog tutorial to not have to worry about setting up their local environment or installing Fly. In one click, they should be able to get into a code editor with the demo application running.
The first time a workspace is opened, a
.env
will be created automatically based on the.env.example
. If the same workspace is closed and re-opened, local changes to this file will be persisted, but it will not be shared between workspaces.If you do want to set a
.env
file and have it be the default for all new workspaces in this repo (useful if you're working on this repo itself or just often use it to start new projects with a similar config), the following command will serialize changes to the.env
file to Gitpod's Workspace Environment Variables and future workspaces will load from that instead of the.env.example
You can test this workflow by clicking this button: