Skip to content

Commit 1f4872a

Browse files
authored
chore: adjust readme
1 parent bd2e39f commit 1f4872a

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

examples/firezone/README.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,16 @@
33
- https://github.com/l4rm4nd/firezone (fork, maintained)
44
- https://github.com/firezone/firezone/tree/legacy (EoL)
55

6+
> [!WARNING]
7+
> Firezone v0.7 has reached End-of-Life on 31st January 2024.
8+
>
9+
> It undergoes a complete redesign (zero-knowledge, cloud) for v1.0 and won't provide any updates for the v0.7 (legacy) branch anymore. More information can be found [here](https://www.firezone.dev/blog/firezone-1-0).
10+
11+
> [!TIP]
12+
> A new fork (l4rm4nd/fireabend) tries to fix outdated dependencies and keep the software alive.
13+
>
14+
> The fork starts with a new v7.0.0 release version and tag.
15+
616
# Notes
717

818
````
@@ -32,13 +42,3 @@ docker compose up -d
3242
Afterwards, the admin mgmt UI is accessible on http://127.0.0.1:13000.
3343

3444
It is recommended to combine Firezone with a TLS reverse proxy such as Traefik as well as with an Identity Provider (IdP) such as Keycloak or Authentik for Single-Sign-On (SSO). Once SSO is enabled, you should disable the possibility for local authentication via the .env file.
35-
36-
> [!WARNING]
37-
> Firezone v0.7 has reached End-of-Life on 31st January 2024.
38-
>
39-
> It undergoes a complete redesign (zero-knowledge, cloud) for v1.0 and won't provide any updates for the v0.7 (legacy) branch anymore. More information can be found [here](https://www.firezone.dev/blog/firezone-1-0).
40-
41-
> [!TIP]
42-
> A new fork (l4rm4nd/fireabend) tries to fix outdated dependencies and keep the software alive.
43-
>
44-
> The fork starts with a new v7.0.0 release version and tag.

0 commit comments

Comments
 (0)