Skip to content

Commit 21f4aae

Browse files
authored
Update README.md
1 parent fea683a commit 21f4aae

File tree

1 file changed

+3
-9
lines changed

1 file changed

+3
-9
lines changed

docker/README.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -18,16 +18,10 @@ chmod 664 /var/log/jinjafx.log
1818
### JinjaFx Server
1919

2020
```
21-
podman create --name jinjafx --tz=local --log-driver=none -v /var/log/jinjafx.log:/var/log/jinjafx.log:Z -p 127.0.0.1:8080:8080 docker.io/cmason3/jinjafx_server:latest -logfile /var/log/jinjafx.log
22-
23-
podman generate systemd -n --restart-policy=always jinjafx | tee /etc/systemd/system/jinjafx.service 1>/dev/null
24-
21+
cp jinjafx.container /etc/containers/systemd/
2522
systemctl daemon-reload
23+
2624
systemctl enable --now jinjafx
2725
```
2826

29-
Once the `jinjafx` container is running you should be able to point your browser at http://127.0.0.1:8080 and it will be passed through to the JinjaFx Server (although the preferred approach is running HAProxy in front of JinjaFx Server so it can deal with TLS termination with HTTP/2 or HTTP/3). I have also included a `jinjafx-run.sh` helper script, which automates the running and updating of the JinjaFx container - if you want to run or update the running container to the container image tagged as "latest" then you can run the following command (it assumes Podman):
30-
31-
```
32-
sudo sh jinjafx-run.sh latest
33-
```
27+
Once the `jinjafx` container is running you should be able to point your browser at http://127.0.0.1:8080 and it will be passed through to the JinjaFx Server (although the preferred approach is running HAProxy in front of JinjaFx Server so it can deal with TLS termination with HTTP/2 or HTTP/3).

0 commit comments

Comments
 (0)