headers
Anfré Littoz | 1 May 2013 12:27
Picon
Favicon

Migration from Apache to Cherokee: URI tweaking

Hi,

Don't know if this the proper place for such a question, so excuse me if this is considered as "noise".

I'm presently testing Cherokee as an alternative to Apache for the LXR project (see http://lxr.sourceforge.net). As long as I use elementary LXR configuration features, it works fine.

But, when I come to try to serve several databases (for short, database is the closest ordinary concept equivalent to its "service") with a single application instance, a trick is played on the URI, which I can't fancy how to convert.

LXR is driver by this kind of URI:

http://hostname/LXR_service_signature/DB_id/script_file/path_for_script?arguments

i.e. an argument-like is interspersed inside the web-path for the script. Under Apache, directive AliasMatch strips off this information and simultaneously routes the request to an alternate document root. The important point is the original URI is not changed and available for parsing unaltered by the script which retrieves the DB_id.

In my conversion attempt, I used either a directory rule (on LXR_service_signature) or regexp rule, both with a redirect handler to remove the DB_id and other non-path related bits. Unhappily, this rewrites the URI and defeats the script processing which no longer can retrieve the DB_id.

Does there exist in Cherokee a means to launch a script whose command line is generated from groups ($1, $2, ...) captured by the regexp-based rule so that the URI is unaltered (environment variables reflect the initial URI)?

ajl
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 4 comments |
headers
Stefan de Konink | 29 Apr 2013 15:59
Picon
Gravatar

New features in separate branches

Hi,

For a very long time, I'm trying to maintain some rules and handlers that 
are not part of the main cherokee distribution and since we are currently 
still focused on solving bugs opposed to introducing more, new features 
get a bitrotten over time.

Since Alvaro has suggested the following page, me git n00b, was already 
experimenting with it. To my suprise with great success, I understood what 
I was doing, and it looked pretty on the network page as well.
<http://nvie.com/posts/a-successful-git-branching-model/>

I started to work to get my older features in a more recent Cherokee 
version and put them in separate branches which it would pull locally for 
a deployment. I have just placed some new code on github that might be 
interesting for more people. Do consider it experimental and not tuned for 
any real world high performance scenario, but very useful for any service 
that implements DBslayer, or some custom API.

<https://github.com/cherokee/webserver/tree/rule_fairuse>

It basically allows to count (based on unique IP address) each request 
that passed by the rule. The rule will match if the predefined limit has 
been exceeded.

Stefan
Permalink | Reply | 0 comments |
headers
vacant server | 27 Apr 2013 13:50

Re: Cherokee Digest, Vol 58, Issue 14




On Apr 27, 2013, at 6:00 AM, cherokee-request <at> lists.octality.com wrote:

Send Cherokee mailing list submissions to
cherokee <at> lists.octality.com

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.octality.com/listinfo/cherokee
or, via email, send a message with subject or body 'help' to
cherokee-request <at> lists.octality.com

You can reach the person managing the list at
cherokee-owner <at> lists.octality.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Cherokee digest..."


Today's Topics:

  1. Re: Migration of website is done. (Daniel Lo Nigro)


----------------------------------------------------------------------

Message: 1
Date: Sat, 27 Apr 2013 11:11:01 +1000
From: Daniel Lo Nigro <lists <at> dan.cx>
To: MATSUU Takuto <matsuu <at> gmail.com>
Cc: cherokee-dev <at> lists.octality.com, cherokee List
<Cherokee <at> lists.octality.com>, Alvaro Lopez Ortega <alvaro <at> alobbs.com>
Subject: Re: [Cherokee] Migration of website is done.
Message-ID:
<CAB1r_+W8GkdgfgiNrCFgLo7AiOx6FMY8LHS3vDR518GDS2wmnA <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Alvaro, perhaps cherokee-project.com should be using an A record for Github
as per their docs for Github Pages on a root domain.

---
Regards,
Daniel

Sent from my phone - please excuse any typos.
On 27/04/2013 9:13 AM, "MATSUU Takuto" <matsuu <at> gmail.com> wrote:

Hi.

cherokee-project.com displays frames with www.cherokee-project.com.
www.cherokee-project redirects to cherokee-project.com. It seems that
redirect loop.

thanks,
matsuu


2013/4/26 Alvaro Lopez Ortega <alvaro <at> alobbs.com>

Thank you very much Makuto.

It should be fixed now.

All the best,
Alvaro


On Fri, Apr 26, 2013 at 4:16 PM, MATSUU Takuto <matsuu <at> gmail.com> wrote:

Hi.

To use CNAME on root domain is invalid as RFC. It has many troubles.

http://blog.cherokee-project.com/ 404
http://planet.cherokee-project.com/ 404
http://forum.cherokee-project.com/ 404
MX record: none.

I propose to use www.cherokee-project.com. IN CNAME cherokee.github.io.

cf.
http://superuser.com/questions/264913/cant-set-example-com-as-a-cname-record

thanks,
matsuu


2013/4/19 Alvaro Lopez Ortega <alvaro <at> alobbs.com>

Great stuff!!


On Fri, Apr 19, 2013 at 12:06 PM, Daniel Lo Nigro <lists <at> dan.cx> wrote:

http://cherokee-project.com/ is now live on Github Pages. Awesome :)



On Fri, Apr 19, 2013 at 12:53 PM, Daniel Lo Nigro <lists <at> dan.cx>wrote:

Thanks Alvaro, I just need someone to merge this commit and then the
CNAME should work :)

https://github.com/cherokee/cherokee.github.com/pull/6


On Fri, Apr 19, 2013 at 12:21 PM, Alvaro Lopez Ortega <
alvaro <at> alobbs.com> wrote:

Hey guys,

cherokee-project.com points now to cherokee.github.io (CNAME).

Best,
Alvaro


On Fri, Apr 12, 2013 at 2:44 PM, Daniel Lo Nigro <lists <at> dan.cx>wrote:

- I believe we should now redirect www.cherokee-project.com to
cherokee.github.io*.

I suggest setting it up as a custom domain (CNAME) rather than
doing a redirect -
https://help.github.com/articles/setting-up-a-custom-domain-with-pages


On Mon, Apr 8, 2013 at 1:18 AM, - - <stadtpirat11 <at> ymail.com> wrote:

Hi all,

I finished the migration of the website.

- I did some changes to the front page and to the downloads page.
I removed the Twitter-Widget because it was empty for months. I added a
JavaScript-widget to have the latest commit messages for "master" and "dev".
- On the downloads page I removed the OS selector because Windows
code has been removed and the Mac OS X page was empty. I consolidated the
Linux guides and the package guide. I also added a quick list do download
the latest sources.

I admit, it is not beautiful, but it will do the job. I hope
someone else will make it pretty. Just fork
https://github.com/cherokee/cherokee.github.com, make your
changes and submit a pull request. :)


Follow-ups:
- I believe we should now redirect www.cherokee-project.com to
cherokee.github.io*.
- Maybe deactivate the wiki of cherokee/cherokee.github.com?
- Redirect or remove record for  bugs.cherokee-project.com.
- Please hide the bugtracker from code.google.com/cherokee.
Issues will remain and can still be reached via the imported issues on
Github, but it will not be visible in the menus on the Google-repository.

Cheers

Stadtpirat

* https://github.com/blog/1452-new-github-pages-domain-github-io

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee





--
Greetings, alo.
http://www.alobbs.com/






--
Greetings, alo.
http://www.alobbs.com/

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee





--
Greetings, alo.
http://www.alobbs.com/



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.octality.com/pipermail/cherokee/attachments/20130427/c2f167d6/attachment-0001.html>

------------------------------

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee


End of Cherokee Digest, Vol 58, Issue 14
****************************************

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
Daniel Lo Nigro | 19 Apr 2013 04:53
Favicon

Re: Migration of website is done.

Thanks Alvaro, I just need someone to merge this commit and then the CNAME should work :)



On Fri, Apr 19, 2013 at 12:21 PM, Alvaro Lopez Ortega <alvaro <at> alobbs.com> wrote:
Hey guys,

cherokee-project.com points now to cherokee.github.io (CNAME).

Best,
Alvaro


On Fri, Apr 12, 2013 at 2:44 PM, Daniel Lo Nigro <lists <at> dan.cx> wrote:
- I believe we should now redirect www.cherokee-project.com to cherokee.github.io*.
I suggest setting it up as a custom domain (CNAME) rather than doing a redirect - https://help.github.com/articles/setting-up-a-custom-domain-with-pages


On Mon, Apr 8, 2013 at 1:18 AM, - - <stadtpirat11 <at> ymail.com> wrote:
Hi all,

I finished the migration of the website.

- I did some changes to the front page and to the downloads page. I removed the Twitter-Widget because it was empty for months. I added a JavaScript-widget to have the latest commit messages for "master" and "dev".
- On the downloads page I removed the OS selector because Windows code has been removed and the Mac OS X page was empty. I consolidated the Linux guides and the package guide. I also added a quick list do download the latest sources.

I admit, it is not beautiful, but it will do the job. I hope someone else will make it pretty. Just fork https://github.com/cherokee/cherokee.github.com, make your changes and submit a pull request. :)


Follow-ups:
- I believe we should now redirect www.cherokee-project.com to cherokee.github.io*.
- Maybe deactivate the wiki of cherokee/cherokee.github.com?
- Redirect or remove record for  bugs.cherokee-project.com.
- Please hide the bugtracker from code.google.com/cherokee. Issues will remain and can still be reached via the imported issues on Github, but it will not be visible in the menus on the Google-repository.

Cheers

Stadtpirat

* https://github.com/blog/1452-new-github-pages-domain-github-io

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee




--
Greetings, alo.
http://www.alobbs.com/ 

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 8 comments |
headers
Daniel Loureiro | 17 Apr 2013 11:13
Picon
Gravatar

Setting a user defined password at cherokee-admin

Hi,

I want to make some changes in cherokee-admin launcher to accept a user-defined password at command line (rather than automatically generate a random password). But I don't known how the sources are structured. Can someone tell me what file (or files) I need to change to do this? Is this https://github.com/cherokee/webserver/blob/master/cherokee/main_admin.c ?

Thanks,
--
Daniel Loureiro
------------------------------
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 3 comments |
headers
M. David Peterson | 13 Apr 2013 08:12
Gravatar

Re: Embedded server


On Fri, Apr 12, 2013 at 9:11 PM, Locke Bircher <locke <at> gigsalad.com> wrote:
Hah, a patch in PDF format!

I know, right?! Whoo! I mean, it may be completely unusable, but it does provide a nice presentation layer for the upper management types who would be completely freaked out if they had to look at a plain ASCII text and try to decipher what the hell they were looking at. ;-)


That's very cool that they are using Cherokee.

Which is certainly cool enough to consider forgiving whomever chose to provide a PDF patch file. Barely, but none-the-less ;-)

--
/M:D

M. David Peterson
Co-Founder & Chief Architect, 3rd&Urban, LLC
e: m.david <at> 3rdandurban.com | v: (503) 332-6230 | w: http://mdavidpeterson.org 
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
- - | 7 Apr 2013 17:18
Favicon
Gravatar

Migration of website is done.

Hi all,

I finished the migration of the website.

- I did some changes to the front page and to the downloads page. I removed the Twitter-Widget because it was
empty for months. I added a JavaScript-widget to have the latest commit messages for "master" and "dev".
- On the downloads page I removed the OS selector because Windows code has been removed and the Mac OS X page
was empty. I consolidated the Linux guides and the package guide. I also added a quick list do download the
latest sources.

I admit, it is not beautiful, but it will do the job. I hope someone else will make it pretty. Just fork
https://github.com/cherokee/cherokee.github.com, make your changes and submit a pull request. :)

Follow-ups:
- I believe we should now redirect www.cherokee-project.com to cherokee.github.io*.
- Maybe deactivate the wiki of cherokee/cherokee.github.com?
- Redirect or remove record for  bugs.cherokee-project.com.
- Please hide the bugtracker from code.google.com/cherokee. Issues will remain and can still be reached
via the imported issues on Github, but it will not be visible in the menus on the Google-repository.

Cheers

Stadtpirat

* https://github.com/blog/1452-new-github-pages-domain-github-io
Permalink | Reply | 3 comments |
headers
Stefan de Konink | 7 Apr 2013 03:33
Picon
Gravatar

Interpreter users (uwsgi/scgi/etc.) ? Keep an eye on this one.

<https://github.com/cherokee/webserver/issues/956>

It seems that we have caught a bug that is very old, and only relevant if 
you develop a lot of code that requires the interpreter to restart. I do 
hope to read some feedback on this oneliner.

I have switched to the following development model;
<http://nvie.com/posts/a-successful-git-branching-model/>

Next to giving pretty pictures on github, it actually makes a lot of sense 
when sending and receiving pull requests. So please do the same :) Create 
a branch when you work on something and do a pull request for that branch.

<https://github.com/cherokee/webserver/network>

Stefan
Permalink | Reply | 0 comments |
headers
- - | 5 Apr 2013 10:53
Favicon
Gravatar

URL structure /index.php/param1/param2

Hi,

I just set up owncloud and only configured the PHP Behaviour rule.

Owncloud uses an URL structure just like http://cloud.example.com/index.php/settings/admin and it's
simply working.

I wonder how that could be without having to configure behviour rules doing internal redirections??

Stadtpirat
Permalink | Reply | 1 comment |
headers
Sergio Aguilar Guerrero | 4 Apr 2013 03:58
Picon
Gravatar

cherokee-remote.py script

Hello All,

I just wanted to share a little script I wrote for managing a remote cherokee server thru SSH.
It's just a remote ssh cherokee-admin helper, it will run cherokee-admin remotely, establish a secure ssh tunnel to the admin port and then open the default browser with the url. It's implemented with python fabric.

I'm still new at python, so the code is a little basic and still needs a bit more work, but currently is functional. I just created it because I was tired of doing the same commands over and over.

I normally use ssh keys, and will probably need to implement something for password caching using fabric.
 
Here's the link:

Please feel free to make any suggestions and improvements; fork if you wish.

Regards,

Sergio Aguilar


PS. I'll be offline for a few days,  will respond when I'm back.
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
Ybotc | 3 Apr 2013 21:34
Picon

Embedded server

Hello all

I have a camera with a built in cherokee servers, to access it you use the
following:

Http://10.5.5.9:8080/

The camera takes videos (.mp4) and low res videos (.lrv) , when accessing
the websever the mime type of the mp4 files is correctly set as video , but
the lrv isn't set so you can't stream the files.

Is there a way of adding a mime type on an embedded version of cherokee ? I
have tried http://10.5.5.9:9090/ but this doesn't bring up the admin pages.

Any help appreciated

Thanks
Toby

--
View this message in context: http://cherokee-web-server-general.1049476.n5.nabble.com/Embedded-server-tp5706841.html
Sent from the Cherokee Web Server - General mailing list archive at Nabble.com.
Permalink | Reply | 8 comments |

Gmane