From 1c4d9ce8a6e8c3ea2797d54e07ada38108d45433 Mon Sep 17 00:00:00 2001 From: Joshua Strobl Date: Fri, 21 Jul 2023 14:13:12 +0300 Subject: [PATCH] Cleanup deploy related info that is no longer relevant --- Dockerfile | 8 -------- README.md | 8 -------- 2 files changed, 16 deletions(-) diff --git a/Dockerfile b/Dockerfile index 2e64731..77c2f13 100644 --- a/Dockerfile +++ b/Dockerfile @@ -8,14 +8,6 @@ RUN yarn EXPOSE 3000 CMD ["yarn", "start", "-h", "0.0.0.0"] -FROM base as deploy -WORKDIR /app -RUN yarn --immutable -RUN yarn build -RUN yarn workspaces focus --all --production -EXPOSE 3000 -CMD ["yarn", "serve", "-h", "0.0.0.0"] - # If you're wondering why we just don't just shove off build/ into nginx, # it's because of how nginx will handle the internal SSL termination and redirection. # Instead we use yarn serve which similar to ghost will just listen on its respective port without question. diff --git a/README.md b/README.md index a096a6c..3d5d325 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,6 @@ To start the live reloading Docusaurus, run: `yarn start` We provide the following targets for our container image: - `development`: This can be used to facilitate local development should you not wish to set up a host-based local development environment. -- `deploy`: This is used in our CI / CD pipeline and is what runs on our infrastructure. ### Using development target for local development @@ -56,13 +55,6 @@ For this section, we will be using [podman](https://podman.io/), although the co This will mount the working directory at `/app` as a volume and whenever there is a change to this directory, Docusaurus will automatically rebuild thanks to hot module reloading. -### Testing deploy - -If you want to test the production image, follow the steps below: - -- Build the image: `podman build -t docusaurus:deploy --target deploy .` -- Run the image: `podman run -it --rm -p 3000:3000 docusaurus:deploy` - ## License - Source code is licensed under Apache-2.0.