From 4ba76e4aa2591556612f5fbf960d21800bc2e627 Mon Sep 17 00:00:00 2001 From: Manav Rathi Date: Wed, 27 Mar 2024 12:46:08 +0530 Subject: [PATCH] Tweaks --- server/docs/docker.md | 6 +++--- server/docs/publish.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/server/docs/docker.md b/server/docs/docker.md index 717a503e56..a6e0e2cd88 100644 --- a/server/docs/docker.md +++ b/server/docs/docker.md @@ -29,8 +29,8 @@ require you to clone the repository or build any images. cd ../.. ``` -3. Modify `compose.yaml`. Instead of asking it to build Ente's server (museum), - we want to get it to pull and use the published Docker image. +3. Modify `compose.yaml`. Instead of building from source, we want directly use + the published Docker image from `ghcr.io/ente-io/server` ```diff --- a/server/compose.yaml @@ -52,7 +52,7 @@ require you to clone the repository or build any images. touch museum.yaml ``` -4. That's it. You can now start everything. +4. That is all. You can now start everything. ```sh docker compose up diff --git a/server/docs/publish.md b/server/docs/publish.md index 5f7be8e447..7984648e4a 100644 --- a/server/docs/publish.md +++ b/server/docs/publish.md @@ -32,6 +32,6 @@ running production instance. Then, trigger the "Publish (server)" workflow, providing it the commit. You can trigger it either from GitHub's UI or using the `gh cli`. With the CLI, we can -combine both these steps too: +combine both these steps too. -Once the workflow completes, the resultant image will be available at +Once the workflow completes, the resultant image will be available at `ghcr.io/ente-io/server`.