Skip to content

Commit 69382b1

Browse files
fix : Readme.md
1 parent fa2b9a6 commit 69382b1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@
5555
- In contrast, Traefik requires the creation and gradual adjustment of various configuration files, which requires your App's docker binary running.
5656

5757

58-
2. **[Beta] Isomorphic local-and-remote runner**
58+
2. Isomorphic local-and-remote runner**
5959
- The same `run.sh` and `.env` drive deployments locally and on remote servers over SSH.
6060
- Remote servers receive the image binary and execute the same pipeline with `GIT_IMAGE_LOAD_FROM=file` (see [Production > GIT_IMAGE_LOAD_FROM=file](#1-git_image_load_fromfile-strategy-without-docker-registry)).
6161
- Behavior stays consistent across environments; only the image source differs (build/registry/file).
@@ -473,7 +473,7 @@ bash check-source-integrity.sh
473473
- Up to this point, your app has been running in a Docker container through the ``bash.run.sh`` command, enabling continuous Blue-Green deployments. However, you may want to deploy the built Docker image independently to another environment, and you likely wouldn't want to leave unnecessary source code, except for the Docker images and configuration files, on the production server.
474474
- The key environment variable enabling this is the ``GIT_IMAGE_LOAD_FROM``. Up to this point, ``GIT_IMAGE_LOAD_FROM`` has been set to ``build``.
475475

476-
### 1. ``GIT_IMAGE_LOAD_FROM=file`` strategy (Beta. without Docker Registry)
476+
### 1. ``GIT_IMAGE_LOAD_FROM=file`` strategy (without Docker Registry)
477477
- With Load Balancer
478478
```mermaid
479479
graph TD;

0 commit comments

Comments
 (0)