ruangrupa/kios-webapp
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Revert "Update start containers command to use npm instead of yarn and update deployment command to use npm instead of yarn prod"

Browse Source 
This reverts commit d541cf9b63.
This commit is contained in:
Max Schmidt 2023-07-28 17:03:25 +02:00
parent 27dfaa8f6a
commit b5e8be0e5d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -49,7 +49,7 @@ You have two options for getting the repository:
Once you've cloned the repository or created your own from the template, follow these steps: Once you've cloned the repository or created your own from the template, follow these steps:
1. Change into the repository directory: `cd {newName}` 1. Change into the repository directory: `cd {newName}`
1. Start the containers: `npm run dev` 1. Start the containers: `yarn dev`
This will start up the Astro, Payloadcms and Mongo containers and make them available on your local machine. Astro will be served at http://localhost:3000 and the Payload will be available at http://localhost:3001. This will start up the Astro, Payloadcms and Mongo containers and make them available on your local machine. Astro will be served at http://localhost:3000 and the Payload will be available at http://localhost:3001.
@ -59,7 +59,7 @@ The `docker-compose.yml` and `docker-compose-dev.yml` files includes everything
## Deployment ## Deployment
Deployment is handled by a Github Actions Workflow on every push. It logs into the server via SSH, pulls or clones the latest version of the repository, and runs `npm run prod`. Deployment is handled by a Github Actions Workflow on every push. It logs into the server via SSH, pulls or clones the latest version of the repository, and runs `yarn prod`.
Because Astro is completely static, a content change in the CMS must trigger a new build of Astro. Therefore, there’s a `payload.yml` workflow that gets triggered by a webhook after every content change from Payload. Because Astro is completely static, a content change in the CMS must trigger a new build of Astro. Therefore, there’s a `payload.yml` workflow that gets triggered by a webhook after every content change from Payload.