I used cherokee-admin and did the following steps: 1. Edit the default virtual host 2. Add a new 'directory' rule with the value /awqaf 3. Used the Redirection Handler 4. In the Rule List I have: + Type: Internal + Regular Expression: (\.+)$ + Substitution: index.php/$1/
Saved and restarted, and now I get a 500 Internal Server Error. Here is the config file lines:
> I used cherokee-admin and did the following steps: > 1. Edit the default virtual host > 2. Add a new 'directory' rule with the value /awqaf > 3. Used the Redirection Handler > 4. In the Rule List I have: > + Type: Internal > + Regular Expression: (\.+)$ > + Substitution: index.php/$1/
> Saved and restarted, and now I get a 500 Internal Server Error. Here is the config file lines:
Wonderful article. It worked for me. What I'm trying to do though is to apply the rule to a subdirectory using the default virtual host. Just like you place an .htaccess file within a directory and it is inherited by the subdirectory. Also, it would be great if a Wizard is created for this. I had a look at the wizard files, and I'm trying to do one for Concrete5.
> Wonderful article. It worked for me. What I'm trying to do though is to apply the rule to a subdirectory using the default virtual host. Just like you place an .htaccess file within a directory and it is inherited by the subdirectory. > Also, it would be great if a Wizard is created for this. I had a look at the wizard files, and I'm trying to do one for Concrete5.
> Wonderful article. It worked for me. What I'm trying to do though is to apply the rule to a subdirectory using the default virtual host. Just like you place an .htaccess file within a directory and it is inherited by the subdirectory. > Also, it would be great if a Wizard is created for this. I had a look at the wizard files, and I'm trying to do one for Concrete5.
For a subdirectory you can add a "Regular Expression" rule and set a redirection handler. Something like: Regular Expression: ^/concrete5/ Handler: Redirection: ^/concrete5/(.*)$ /concrete5/index.php/$1
And, of course, add the subdirectory to the other concrete5 rules. Leaving the default at List & Send.
Te hard part is getting the configuration right. Believe me, I know. I've just uploaded a dozen or so that should be shipped with 0.99.25. If people posted their working cherokee.conf samples, most Wizards could be coded in a breeze.
> Wonderful article. It worked for me. What I'm trying to do though is to apply the rule to a subdirectory using the default virtual host. Just like you place an .htaccess file within a directory and it is inherited by the subdirectory. > Also, it would be great if a Wizard is created for this. I had a look at the wizard files, and I'm trying to do one for Concrete5.
Taher Shihadeh dijo [Fri, Oct 09, 2009 at 07:41:12PM +0200]:
> Te hard part is getting the configuration right. Believe me, I know. > I've just uploaded a dozen or so that should be shipped with 0.99.25. > If people posted their working cherokee.conf samples, most Wizards could > be coded in a breeze.
Umh... Just thinking out loud: I think many similar issues could be solved (or helped) by showing clueless users exactly what portions of the configuration are generated by a particular screen/entry in cherokee-admin.
Of course, there are _lots_ of possible ways to implement this, but I'm sure it would:
Increase the contributions you mention Increase the amount of "well, duh!" moments, where users find out obvious things they would have not find otherwise Make it easier to give support to users not understanding the whole working of the server
Before logging this as a bug^Wrequest for enhancement, what would you think?
-- Gunnar Wolf gw...@gwolf.org (+52-55)5623-0154 / 1451-2244 _______________________________________________ Cherokee mailing list Chero...@lists.octality.com http://lists.octality.com/listinfo/cherokee
What would you suggest, popping-up the info with something like Growl? (although it isn't really useful until it is saved on disk, since rule priorities change on the fly). Actually I think this would be useful for the expert users, not for the clueless ones. Could you elaborate, please? :)
Regarding my previous message, I insist: any one wanting a wizard for a favorite app is encouraged to send a working cherokee.conf ready for the application. It *will* certainly boost that wizard up in the creation queue ;-)
Gunnar Wolf wrote: > Taher Shihadeh dijo [Fri, Oct 09, 2009 at 07:41:12PM +0200]:
>> Te hard part is getting the configuration right. Believe me, I know. >> I've just uploaded a dozen or so that should be shipped with 0.99.25. >> If people posted their working cherokee.conf samples, most Wizards could >> be coded in a breeze.
> Umh... Just thinking out loud: I think many similar issues could be > solved (or helped) by showing clueless users exactly what portions of > the configuration are generated by a particular screen/entry in > cherokee-admin.
> Of course, there are _lots_ of possible ways to implement this, but > I'm sure it would:
> Increase the contributions you mention > Increase the amount of "well, duh!" moments, where users find out > obvious things they would have not find otherwise > Make it easier to give support to users not understanding the whole > working of the server
> Before logging this as a bug^Wrequest for enhancement, what would you > think?
>> Wonderful article. It worked for me. What I'm trying to do though is to apply the rule to a subdirectory using the default virtual host. Just like you place an .htaccess file within a directory and it is inherited by the subdirectory. >> Also, it would be great if a Wizard is created for this. I had a look at the wizard files, and I'm trying to do one for Concrete5.
> Yeah!, a Wizard would be great... go for it! ;-)
I was wondering if you had any luck, were still interested and/or needed help with this. In any case, I would really appreciate it if you could log a request for enhancement in our bug track (http://bugs.cherokee-project.com), and attach your working cherokee.conf to it. That way we won't loose track of the issue, and someone could pick up the task of doing the wizard in case you wouldn't finish it for whatever reason.
> I was wondering if you had any luck, were still interested > and/or needed help with this. > In any case, I would really appreciate it if you could log > a request for enhancement in our bug track (http://bugs.cherokee-project.com), and attach your > working cherokee.conf to it. That way we won't loose track > of the issue, and someone could pick up the task of doing > the wizard in case you wouldn't finish it for whatever > reason.
I was trying to compile 0.99.25 on Debian Testing today, but after finishing successfully it didn't start. Is there an easy way to build a .deb package for Debian, or if you can tell me what are the most suitable parameters to use with 'configure' to install and run it smoothly on Debian Testing.
Anyway, I'll give it another shot tomorrow and get back to you.
Ossama Khayat wrote: > I was trying to compile 0.99.25 on Debian Testing today, but after finishing successfully it didn't start. Is there an easy way to build a .deb package for Debian, or if you can tell me what are the most suitable parameters to use with 'configure' to install and run it smoothly on Debian Testing.
I guess Gunnar and Leonel are the guys to go for this one ;-) Me, I just use checkinstall from time to time (or not even that, which I'm sure will be frowned upon by our local experts). Anyway, it is strange that Cherokee is built but wouldn't run. Did you try to launch a cherokee-worker by hand to see what's wrong (maybe even with CHEROKEE_TRACE or using an alternative config file)?
> Anyway, I'll give it another shot tomorrow and get back to you.
----- Original Message ---- > From: Taher Shihadeh <ta...@unixwars.com> [...] > I guess Gunnar and Leonel are the guys to go for this one ;-) Me, I just use > checkinstall from time to time (or not even that, which I'm sure will be frowned > upon by our local experts). Anyway, it is strange that Cherokee is built but > wouldn't run. Did you try to launch a cherokee-worker by hand to see what's > wrong (maybe even with CHEROKEE_TRACE or using an alternative config file)?
Regarding Concrete5, It's working very fast and using clean URLs. I create a virtual host 'concrete', added a 127.0.0.1 concrete to my /etc/hosts and it's working perfect. Attached is my config.
One thing though, I didn't know how to run it as a subdirectory in my 'Default' virtual server.
Ossama Khayat dijo [Mon, Oct 26, 2009 at 03:28:12PM -0700]:
> I was trying to compile 0.99.25 on Debian Testing today, but after > finishing successfully it didn't start. Is there an easy way to > build a .deb package for Debian, or if you can tell me what are the > most suitable parameters to use with 'configure' to install and run > it smoothly on Debian Testing.
> Anyway, I'll give it another shot tomorrow and get back to you.
I uploaded it to Sid, still using the old-but-tried build method :-) You can download the source package (the orig.tar.gz / .dsc / .diff.gz linked from that page), and that should build cleanly on your Testing system.
-- Gunnar Wolf gw...@gwolf.org (+52-55)5623-0154 / 1451-2244 _______________________________________________ Cherokee mailing list Chero...@lists.octality.com http://lists.octality.com/listinfo/cherokee