Skip to content

Project output path #16

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

Open
benneynens opened this issue Jul 16, 2023 · 1 comment
Open

Project output path #16

benneynens opened this issue Jul 16, 2023 · 1 comment

Comments

@benneynens
Copy link

Stuck on the Getting started instructions.

What are we supposed to use for the Project output path, when running sanity init --env?

If you just leave the default path it just creates a brand new Sanity project, so you have a new Sanity project within each the App and Studio folders. That doesn't make sense to me. Meanwhile, you can't select a folder that already has files in it.

Isn't the Studio folder supposed to be where the sanity project is? Ie. not a subfolder of Studio or App.

@benneynens
Copy link
Author

Just to explain my process a little further:

  1. clone this project
  2. cd into app folder, then npm install
  3. sanity init --env
  4. select my sanity project
  5. leave the default output path as is, ie. app/myprojectname
  6. repeat steps 2-5 in Studio folder

Doesn't work. No env files created and it would seem to me duplicate Sanity projects (ie. one in each of App and Studio folders).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant