What's new
Added a feature to serve cronicle app on subpath, e.g. http://localhost:3012/cronicle. Big thanks to @mjavah
To enable add top level config ```"base_path": "/cronicle"`` to config.json, or set via CRONICLE_base_path=/cronicle variable
Notes:
- this config should follow pattern /xxxx where x is alphanumeric character
- if using cluster - this setting should be same on master and worker nodes
- if that config is not set - everything will work as before (no adjustment needed)
- this is mainly meant to use for reverse proxy. Now you can just create single proxy pass like https://proxy/cronicle => localhost:3012/cronicle, no need to configure socket.io, API or content paths. E.g.
http {
include mime.types;
default_type application/octet-stream;
# Other configurations...
server {
listen 80;
server_name localhost;
location /cronicle/ {
client_max_body_size 2048m;
proxy_read_timeout 86400s;
proxy_send_timeout 86400s;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_http_version 1.1;
proxy_redirect off;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_pass http://localhost:3012/cronicle/;
}
}
}Fixes:
- Fixed some minor last status rendering issues on schedule page