luciash: hi Bsfez refizul: polom arildb__: joined #tikiwiki arildb_: joined #tikiwiki kstingel: joined #tikiwiki arildb__: joined #tikiwiki kstingel1: joined #tikiwiki fabricius: joined #tikiwiki kstingel: joined #tikiwiki arildb_: joined #tikiwiki arildb__: joined #tikiwiki kstingel1: joined #tikiwiki goj_killedByISP: joined #tikiwiki Bsfez: polom arildb_: joined #tikiwiki arildb__: joined #tikiwiki hrsms: joined #tikiwiki jacmoe: joined #tikiwiki kstingel1: joined #tikiwiki gour: joined #tikiwiki USlacker: joined #tikiwiki fabricius: joined #tikiwiki gour: i wonder if someone is using tiki with webserver behind reverse-proxy? changi: gour: yes i am dennmans: joined #tikiwiki gour: changi: is there any issue with it? i've tried with lighttpd, cherokee & hiawatha (all behind nginx) and all three get local port on which the server is listening appended to the URL. the only difference is that hiawatha & lighty are not working with such URls, while cherokee, somehow, does it
changi: does tiki require some special setup in such case or not, iow. does it strongly feels as nginx at the front-end is misconfigured? redflo: joined #tikiwiki RobertPlummerMob: joined #tikiwiki
joined #tikiwiki
joined #tikiwiki
joined #tikiwiki changi: gour: i think your nginx is misconfigured, because we have 30 tiki and 200 other website which are working like a charm gour: changi: thank you. i may try account at webfaction to be sure
changi: which servers are used as back-ends behind nginx? fabricius: joined #tikiwiki kstingel1: who is the Developer workin on API Docs?
^ *working kstingel: joined #tikiwiki changi: gour: apache 2.2 Tiki-KGB: tikiwiki 03changi67 r44216 10(9 files in 7 dirs)
tikiwiki [MRG] Automatic merge, branches/10.x 44197 to 44213 vmachine: joined #tikiwiki gour: changi: do you have any experience using lighttpd/cherokee/hiawatha as servers running behind nginx as reverse proxy? does apache listen on non-80 port? changi: no i don't, apache is listening on 80 gour: that could be the catch. my server are listening on non-80 port
the guy from ISP is asking me if i can find out about proper reverse-proxy setup. he even sent me current config...you may take a look if you're familiar with nginx? changi: gour: just send it by email gour: changi: private or tiki-devel? changi: gour: as you want gour: changi: i'll send it to tiki-devel...more eyes ;) changi: ok Tiki-KGB: tikiwiki 03changi67 r44217 10trunk/ 10(22 files in 16 dirs)
tikiwiki no change, only fix some violation - see qa.tiki.org changi: vi lib/metadata/reconcile.php -: changi wront term :) gour: changi: i sent the post RobertPlummerMob: joined #tikiwiki -: gour hopes it's not some tiki-10beta and/or some tiki-routing-related problem changi: gour: ok, will have a look gour: changi: thanks a lot Tiki-KGB: tikiwiki 03kstingel r44218 10trunk/ 10tiki-objectpermissions.php 10tiki-index.php 10tiki-share.php
tikiwiki [REF] correction of PHPDoc commenting
tikiwiki 03changi67 r44219 10trunk/ 10(32 files in 23 dirs)
tikiwiki no change, only fix some violation - see qa.tiki.org changi: gour: i have my configuration at work, will send you our configuration on monday
gour: just remind me if i forgot :) gour: changi: ok. although i still have concern whether tiki is capable to run behind reverse-proxy server running on non-80 port...see http://forums.modx.com/index.php?topic=54214.0 that was the reason i had to abandon MODx in the past Tiki-KGB: tikiwiki 03changi67 r44220 10trunk/ 10(9 files in 7 dirs)
tikiwiki no change, only fix some violation - see qa.tiki.org changi: gour: i've just try it with apache -> apache:81, and it's working gour: changi: thank you...that's encouraging to hear...let's hope it's not another of apache-only thingies changi: gour: ok, just create a POC with nginx as reverse proxy and apache on port 81 as web server,
gour: and it's working :) gour: changi: cool, cool...i've to try with non-apache server as well ;) changi: gour: finaly, nginx as reverse-proxy with nginx as web server => and it's :.....................;
gour: working :) gour: changi: thanks...encouraging...i may try tomorrow (n my localhost) with nginx & hiawatha
however, it looks that tiki is ready :-)