Manav Rathi 1 年之前
父節點
當前提交
4ba76e4aa2
共有 2 個文件被更改,包括 5 次插入5 次删除
  1. 3 3
      server/docs/docker.md
  2. 2 2
      server/docs/publish.md

+ 3 - 3
server/docs/docker.md

@@ -29,8 +29,8 @@ require you to clone the repository or build any images.
     cd ../..
     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
     ```diff
     --- a/server/compose.yaml
     --- a/server/compose.yaml
@@ -52,7 +52,7 @@ require you to clone the repository or build any images.
    touch museum.yaml
    touch museum.yaml
    ```
    ```
 
 
-4. That's it. You can now start everything.
+4. That is all. You can now start everything.
 
 
    ```sh
    ```sh
    docker compose up
    docker compose up

+ 2 - 2
server/docs/publish.md

@@ -32,6 +32,6 @@ running production instance.
 
 
 Then, trigger the "Publish (server)" workflow, providing it the commit. You can
 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
 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`.