Cleanup deploy related info that is no longer relevant

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.

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.