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

Add instructions on how to set up Fauna and Zeit for local development #26

Open
odbol opened this issue Apr 30, 2020 · 2 comments · May be fixed by #27
Open

Add instructions on how to set up Fauna and Zeit for local development #26

odbol opened this issue Apr 30, 2020 · 2 comments · May be fixed by #27
Labels
ℹ️ docs Improvements or additions to documentation
Projects

Comments

@odbol
Copy link

odbol commented Apr 30, 2020

I tried following the Readme instructions to get a local dev copy going, however I got stuck on the now part:

02:19:26 ~/Documents/Development/HTML/bsa/dual-power-app |feature/readme ✗| →  now
Now CLI 18.0.0
? Set up and deploy “~/Documents/Development/HTML/bsa/dual-power-app”? [Y/n] y
? Which scope do you want to deploy to? odbol
? Link to existing project? [y/N] n
? What’s your project’s name? dual-power-app
? In which directory is your code located? ./
Auto-detected project settings (Next.js):
- Build Command: `npm run build` or `next build`
- Output Directory: Next.js default
- Development Command: next dev --port $PORT
? Want to override the settings? [y/N] n
Error! Environment Variable "FAUNADB_SECRET" references Secret "faunadb-secret-********", which does not exist.
@replygirl
Copy link
Contributor

replygirl commented Apr 30, 2020

i'll get on this today. thank you for bringing my attention to it!!

@odbol for now, here's what you need to do:

  1. create a personal fauna account
  2. create a database
  3. create a key for your .env file
  4. upload the schema in the "graphql" page of your fauna console

if you need to deploy to your own vercel (formerly zeit) project, there is an integration that will add your fauna key to your vercel project.

you can also skip vercel altogether using yarn dev

@replygirl replygirl added the ℹ️ docs Improvements or additions to documentation label Apr 30, 2020
@replygirl replygirl added this to Needs triage in Docs via automation Apr 30, 2020
@replygirl replygirl moved this from Needs triage to High priority in Docs Apr 30, 2020
@replygirl replygirl linked a pull request May 1, 2020 that will close this issue
4 tasks
@replygirl replygirl linked a pull request May 1, 2020 that will close this issue
4 tasks
@replygirl
Copy link
Contributor

@odbol #27 overhauls the environment so you don't have to set up now at all if you don't want to! There are now two options:

  • Follow additional instructions in README.md to configure your environment for API development
  • Run yarn dev-remote, which will use our hosted dev API

@replygirl replygirl removed their assignment May 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ℹ️ docs Improvements or additions to documentation
Projects
No open projects
Docs
  
High priority
Development

Successfully merging a pull request may close this issue.

2 participants