headers
Eric S. Johansson | 3 Mar 2007 18:48

upgrading to 0.5.6

yes, I know my bit behind the times.  I'm trying to upgrade it on ubuntu 
  5.10 ( yes, I know I'm late in upgrading to 6.06).

The problem is: /usr/local/lib/libcherokee-server.so.0: undefined 
reference to `cherokee_header_get_arguments'

If there's a quick patch, fantastic if not, well time to move everything 
over to a virtual machine.  Everything else is fairly easy but mailman 
just sucks.

Many thanks for the help
--

-- 
Speech-recognition in use.  It makes mistakes, I correct some.
Permalink | Reply | 1 comment |
headers
Alvaro Lopez Ortega | 6 Mar 2007 18:53
Picon
Gravatar

Re: upgrading to 0.5.6

Eric S. Johansson wrote, On 03/03/07 18:48:

 > The problem is: /usr/local/lib/libcherokee-server.so.0: undefined
 > reference to `cherokee_header_get_arguments'

   It seems that you are mixing different Cherokee versions. I bet it
   has something to do with two different installations over /usr and
   /usr/local.

   Good luck!

--

-- 
Greetings, alo.
http://www.alobbs.com
Permalink | Reply | 0 comments |
headers
Alvaro Lopez Ortega | 17 Mar 2007 02:34
Picon
Gravatar

New documentation system

Hi,

   Could you please guys take a look at this bug and tell me if you
   know some documentation system similar to what we have been talking
   so far:

      http://www.cherokee-project.com/bugs/ticket/136

   It seems like the best of the approaches to get ride of the current
   Wiki and distribution systems.

--

-- 
Greetings, alo.
http://www.alobbs.com
Permalink | Reply | 4 comments |
headers
Andres Vargas - zodman | 17 Mar 2007 07:01
Picon
Gravatar

Re: New documentation system

mmmmmmmmmmm

im thing the best way to write documentation and contrib with documentation is writen on wiki

cheers

2007/3/16, Alvaro Lopez Ortega < alvaro <at> gnu.org>:
Hi,

   Could you please guys take a look at this bug and tell me if you
   know some documentation system similar to what we have been talking
   so far:

      http://www.cherokee-project.com/bugs/ticket/136

   It seems like the best of the approaches to get ride of the current
   Wiki and distribution systems.

--
Greetings, alo.
http://www.alobbs.com
_______________________________________________
Cherokee mailing list
Cherokee <at> cherokee-project.com
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee

_______________________________________________
Cherokee mailing list
Cherokee <at> cherokee-project.com
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
Permalink | Reply | 3 comments |
headers
Alvaro Lopez Ortega | 17 Mar 2007 12:55
Picon
Gravatar

Re: New documentation system

Andres Vargas - zodman wrote, On 17/03/07 07:01:

 >        Could you please guys take a look at this bug and tell me if
 >        you know some documentation system similar to what we have
 >        been talking so far:
 >
 >           http://www.cherokee-project.com/bugs/ticket/136
 >
 >        It seems like the best of the approaches to get ride of the
 >        current Wiki and distribution systems.
 >
 > im thing the best way to write documentation and contrib with
 > documentation is writen on wiki

   I would agree with you if we weren't suffered spamming problems and
   defaces previously. (damn it! we won't buy your ring-tones; not now,
   not ever, so stop messing!)

   Besides, it's kind of difficult to extract its content and convert
   it to a different format..

   With the wiki we gain simplicity, but the "text in the repository"
   system we would gain flexibility and in some sense security.

   So.. what do you guys think of it?  We're still on time for making a
   decision for 0.6 :-)

--

-- 
Greetings, alo.
http://www.alobbs.com
Permalink | Reply | 2 comments |
headers
Eric S. Johansson | 17 Mar 2007 14:45

Re: New documentation system

Alvaro Lopez Ortega wrote:
>    I would agree with you if we weren't suffered spamming problems and
>    defaces previously. (damn it! we won't buy your ring-tones; not now,
>    not ever, so stop messing!)

http://moinmoin.wikiwikiweb.de/MoinMoinFeatures
see advanced features:

access control lists (see HelpOnAccessControlLists)
optional login with username and password
can reuse authentication done by web server (see HelpOnAuthentication)
modular authentication makes it easy to support single-sign-on (1.5)

> 
>    Besides, it's kind of difficult to extract its content and convert
>    it to a different format..

ReStructuredText support
Can be used to edit DocBook pages and generate DocBook from wiki markup. 
(1.3.5)
Some AntiSpamFeatures
Slideshows, see HelpOnSlideShows.
Twiki draw included, accessable by drawing:some_name. See 
OliverGraf/TWikiDrawPlugin.
formatters to produce something other than HTML (see FormatterMarket)

> 
>    With the wiki we gain simplicity, but the "text in the repository"
>    system we would gain flexibility and in some sense security.

access control lists (see HelpOnAccessControlLists)
optional login with username and password
can reuse authentication done by web server (see HelpOnAuthentication)
modular authentication makes it easy to support single-sign-on (1.5)

one could write a plugin to checkin every change.

--

-- 
Speech-recognition in use.  It makes mistakes, I correct some.
Permalink | Reply | 0 comments |
headers
Eric S. Johansson | 18 Mar 2007 04:58

how .bzr

can't seem to make cherokee serve up a bzr repository.
http://harvee.org/public/akasha/  should have a .bzr file in it as 
should http://harvee.org/public/

what magic am I missing?

esj <at> base606:~/xxx$ bzr branch http://harvee.org/public/akasha
bzr: ERROR: Invalid http response for 
http://harvee.org/public/akasha/.bzr/repository/format: Unable to handle 
http code 500: expected 200 or 404 for full response.
esj <at> base606:~/xxx$

make cherokee output:
buffer.c:535: ERROR: read(-1, 4096,..) -> errno=9 'Bad file descriptor'

--------- wireshark trace --------

GET /public/akasha/.bzr/branch-format HTTP/1.1

User-Agent: bzr/0.15.0candidate2 (pycurl)

Host: harvee.org

Accept: */*

Cache-control: max-age=0

Pragma: no-cache

Connection: Keep-Alive

HTTP/1.1 200 OK

Connection: Keep-Alive

Keep-Alive: timeout=60

Date: Sat, 17 Mar 2007 23:52:14 GMT-4

Server: Cherokee/0.5.6 (UNIX)

Etag: 45c3fdff=23

Last-Modified: Sat, 03 Feb 2007 03:14:07 GMT

Content-Length: 35

Bazaar-NG meta directory, format 1
GET /public/akasha/.bzr/branch/format HTTP/1.1

User-Agent: bzr/0.15.0candidate2 (pycurl)

Host: harvee.org

Accept: */*

Cache-control: max-age=0

Pragma: no-cache

Connection: Keep-Alive

HTTP/1.1 200 OK

Connection: Keep-Alive

Keep-Alive: timeout=60

Date: Sat, 17 Mar 2007 23:52:14 GMT-4

Server: Cherokee/0.5.6 (UNIX)

Etag: 45c3fdff=1a

Last-Modified: Sat, 03 Feb 2007 03:14:07 GMT

Content-Length: 26

Bazaar-NG branch format 5
GET /public/akasha/.bzr/repository/format HTTP/1.1

User-Agent: bzr/0.15.0candidate2 (pycurl)

Host: harvee.org

Accept: */*

Cache-control: max-age=0

Pragma: no-cache

Connection: Keep-Alive

HTTP/1.1 500 Internal Server Error

Connection: Close

Date: Sat, 17 Mar 2007 23:52:14 GMT-4

Server: Cherokee/0.5.6 (UNIX)

Content-Type: text/html

Content-length: 224

Cache-Control: no-cache

Pragma: no-cache

P3P: CP=3DNOI NID CURa OUR NOR UNI

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<html><head><title>500 Internal Server Error</title></head><body><h1>500 
Internal Server Error</h1><p><hr><address>Cherokee web server 0.5.6 Port 
80</address></body></html>
--

-- 
Speech-recognition in use.  It makes mistakes, I correct some.
Permalink | Reply | 0 comments |
headers
Gunnar Wolf | 19 Mar 2007 20:14
Gravatar

Re: New documentation system

Alvaro Lopez Ortega dijo [Sat, Mar 17, 2007 at 12:55:30PM +0100]:
>    I would agree with you if we weren't suffered spamming problems and
>    defaces previously. (damn it! we won't buy your ring-tones; not now,
>    not ever, so stop messing!)
> 
>    Besides, it's kind of difficult to extract its content and convert
>    it to a different format..
> 
>    With the wiki we gain simplicity, but the "text in the repository"
>    system we would gain flexibility and in some sense security.
> 
>    So.. what do you guys think of it?  We're still on time for making a
>    decision for 0.6 :-)

Well, with ikiwiki you can have a Wiki backed on SVN :)

Greetings,

--

-- 
Gunnar Wolf - gwolf <at> gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5 27AF
Permalink | Reply | 0 comments |
headers
L. Kliemann | 28 Mar 2007 10:56
Picon

virtual hosting and TLS

It should be possible, using the extension described in Section 3.1 of RFC 
4366 to have different host keys for different virtual hosts. I tried this 
with the latest Cherokee release. It was promising that one obviously can use 
SSLCertificateFile and friends inside of a virtual host definition, i.e.  
inside of a ``Server example.com { ... }'' construct.  Unfortunately, 
however, in all variations I tried, always the host key of the default host 
was used. This means that Cherokee served files from the DocumentRoot defined 
for the proper virtual host, but not with the host key given inside of the 
virtual host definition.

Is such a feature implemented at all? Can it be expected to be implemented 
some day? It would be VERY convenient not having to use multiple IP addresses 
for different HTTPS sites.

Regards, Lasse
Permalink | Reply | 0 comments |

Gmane