From b5e8be0e5d1b176995e6a389a3176cd76bedfbb9 Mon Sep 17 00:00:00 2001 From: Max Schmidt Date: Fri, 28 Jul 2023 17:03:25 +0200 Subject: [PATCH] Revert "Update start containers command to use npm instead of yarn and update deployment command to use npm instead of yarn prod" This reverts commit d541cf9b63ad37da84cac1c953feea1a2f0c152f. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f5e5bbb..3c14cf5 100644 --- a/README.md +++ b/README.md @@ -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: 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. @@ -59,7 +59,7 @@ The `docker-compose.yml` and `docker-compose-dev.yml` files includes everything ## 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.