forked from Weaverse/pilot
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'Weaverse:main' into main
- Loading branch information
Showing
6 changed files
with
1,458 additions
and
473 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
## Setup for using Customer Account API (`/account`) | ||
|
||
1. Run development with `--customer-account-push__unstable` flag to start the server with a tunnel to expose the local server to the public domain. | ||
|
||
```bash | ||
shopify hydrogen dev --codegen --port 3456 --customer-account-push__unstable | ||
``` | ||
|
||
Or quicker way with: | ||
|
||
```bash | ||
npm run dev:ca | ||
``` | ||
|
||
### Include public domain in Customer Account API settings | ||
|
||
After run the server with `--customer-account-push__unstable` flag, you will get a public domain like `https://<your-cf-tunnel>.tryhydrogen.dev`. And it should be automatically added to the Customer Account API settings. If not, you can manually add it by following these steps: | ||
|
||
1. Go to your Shopify admin => `Hydrogen` or `Headless` app/channel => Customer Account API => Application setup | ||
2. Edit `Callback URI(s)` to include `https://<your-cf-tunnel>.tryhydrogen.dev/account/authorize` | ||
3. Edit `Javascript origin(s)` to include your public domain `https://<your-tunnel>.tryhydrogen.dev` or keep it blank | ||
4. Edit `Logout URI` to include your public domain `https://<your-tunnel>.tryhydrogen.dev` or keep it blank |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,25 +1,25 @@ | ||
### How to make your own project in sync with the original pilot project | ||
|
||
Once you've cloned the pilot project, and put it into your own github account, you'll want to keep it in sync with the | ||
Once you've cloned the pilot project, and put it into your own Github account, you'll want to keep it in sync with the | ||
original pilot project. This is a good idea because the original pilot project will be updated with new features and bug | ||
fixes. | ||
Here is the manual way to do it with rsync: | ||
|
||
1. Clone the original pilot project into a directory called `pilot`: | ||
Here is the manual way to do it with `rsync`: | ||
|
||
1. Clone the latest `pilot` project into a directory called `pilot`: | ||
|
||
```bash | ||
git clone [email protected]:Weaverse/pilot.git | ||
``` | ||
|
||
2. Put your own pilot project into a same level directory. | ||
|
||
3. Run the following command to sync your project with the original pilot project, Keep in mind to | ||
replace `your-pilot-project` with the name of your own pilot project. | ||
3. Run the following command to sync your project with the original pilot project, Keep in mind to replace `your-pilot-project` with the name of your own pilot project. | ||
|
||
```bash | ||
rsync -arv --exclude=node_modules --exclude=.git --exclude=.cache --exclude=.turbo --exclude=dist --exclude=.env ./pilot/ ./your-pilot-project | ||
rsync -arv --exclude=node_modules --exclude=.git --exclude=.cache --exclude=.turbo --exclude=dist --exclude=.env ./pilot/ ./<your-pilot-project> | ||
``` | ||
|
||
4. Commit and push your changes to your own pilot project. | ||
5. It is recommended to run the sync command every time you want to update your project with the latest changes from the | ||
original pilot project. | ||
|
||
5. It is recommended to run the sync command every time you want to update your project with the latest changes from the original pilot project. |
Oops, something went wrong.