ForgeFlux
/
ftest-nginx-proxy
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2 Commits 1 Branch 0 Tags 31 KiB
Shell 74.9%
Dockerfile 25.1%
Go to file
Aravinth Manivannan 4f1915030c
ci/woodpecker/push/woodpecker Pipeline was successful Details
fix: listen on port 80 		2023-10-04 19:16:30 +05:30
.woodpecker.yml feat: import from ForgeFlux/ftest/nginx 2023-10-03 23:36:52 +05:30
Dockerfile feat: import from ForgeFlux/ftest/nginx 2023-10-03 23:36:52 +05:30
README.md feat: import from ForgeFlux/ftest/nginx 2023-10-03 23:36:52 +05:30
init.sh feat: import from ForgeFlux/ftest/nginx 2023-10-03 23:36:52 +05:30
nginx.conf fix: listen on port 80 2023-10-04 19:16:30 +05:30

README.md

status-badge

ftest creates a Docker network called ftest and runs job containers on it. Job containers upload results back to the ftest server. This should work fine, when ftest server is running as a container and is part of the container network. But when developing or when using the (WIP) CLI tool, this isn't feasible.

So this simple nginx proxy configuration exists to expose ftest server running on port 29130 on host machine to the ftest network.