mirror of
https://github.com/ZeppelinBot/Zeppelin.git
synced 2025-03-14 21:31:50 +00:00
e146ed6416
Since Zeppelin was only creating a self-signed certificate, this gave a false sense of security when in reality you'd always want to have a proxy with a proper certificate in front of this anyway. Additionally, generating the certificate at build time meant that the domain couldn't easily be changed/updated without rebuilding.
23 lines
663 B
Text
23 lines
663 B
Text
server {
|
|
listen 80 default_server;
|
|
server_name _;
|
|
|
|
# Using a variable here stops nginx from crashing if the dev container is restarted or becomes otherwise unavailable
|
|
set $backend_upstream "http://api:3001";
|
|
set $dashboard_upstream "http://dashboard:3002";
|
|
|
|
location / {
|
|
# Using a variable in proxy_pass also requires resolver to be set.
|
|
# This is the address of the internal docker compose DNS server.
|
|
resolver 127.0.0.11;
|
|
proxy_pass $dashboard_upstream$uri$is_args$args;
|
|
}
|
|
|
|
location /api {
|
|
resolver 127.0.0.11;
|
|
proxy_pass $backend_upstream$uri$is_args$args;
|
|
proxy_redirect off;
|
|
|
|
client_max_body_size 200M;
|
|
}
|
|
}
|