As it is now, all the base paths are hard coded to "/", which breaks everything if you try to run the webadmin behind a proxy (eg. nginx) and change the base path.
ie, remapping "http://example.com/znc" to "http://127.0.0.1:6667"
All the CSS, which is assumed to be on "/pub/default.css", actually exists on "/znc/pub/default.css", and links (such as /login), don't route to the right place.
As it is now, all the base paths are hard coded to "/", which breaks everything if you try to run the webadmin behind a proxy (eg. nginx) and change the base path.
ie, remapping "http://example.com/znc" to "http://127.0.0.1:6667"
All the CSS, which is assumed to be on "/pub/_default_.css", actually exists on "/znc/pub/_default_.css", and links (such as /login), don't route to the right place.
<!-- github-sync-id:54035623 -->
Not as of 1.5 (currently unreleased / use nightlies)
https://github.com/znc/znc/commit/4376b373d841253c8a6dac4207567d4661724432
<!-- github-comment-id:69548373 -->
I just noticed it was a config option for 1.6 on the wiki (along with customizing SSL, yay!).
Is 1.5 the latest release? The wiki says 1.4 is latest.
I just noticed it was a config option for 1.6 on the wiki (along with customizing SSL, yay!).
Is 1.5 the latest release? The wiki says 1.4 is latest.
<!-- github-comment-id:69599711 -->
Odd points are development versions, even points are stable releases. 1.4 is the latest stable release, but you can run 1.5 (git/devel) by checking out and compiling the code in this repo.
Odd points are development versions, even points are stable releases. 1.4 is the latest stable release, but you can run 1.5 (git/devel) by checking out and compiling the code in this repo.
<!-- github-comment-id:69600091 -->
@jpnurmi http://wiki.znc.in/Configuration#Added_in_1.6 Could just name it "1.5 (git/nightly)" instead of "1.6", since 1.6 is not released yet.
<!-- github-comment-id:69644275 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As it is now, all the base paths are hard coded to "/", which breaks everything if you try to run the webadmin behind a proxy (eg. nginx) and change the base path.
ie, remapping "http://example.com/znc" to "http://127.0.0.1:6667"
All the CSS, which is assumed to be on "/pub/default.css", actually exists on "/znc/pub/default.css", and links (such as /login), don't route to the right place.
Not as of 1.5 (currently unreleased / use nightlies)
https://github.com/znc/znc/commit/4376b373d841253c8a6dac4207567d4661724432
I just noticed it was a config option for 1.6 on the wiki (along with customizing SSL, yay!).
Is 1.5 the latest release? The wiki says 1.4 is latest.
Odd points are development versions, even points are stable releases. 1.4 is the latest stable release, but you can run 1.5 (git/devel) by checking out and compiling the code in this repo.
ZNC versioning strikes again: https://github.com/znc/znc/issues/748
@jpnurmi http://wiki.znc.in/Configuration#Added_in_1.6 Could just name it "1.5 (git/nightly)" instead of "1.6", since 1.6 is not released yet.
Duplicate of #480