Thank you for your reply, it helped me alot!
once I figured out that I needed to install the admin package first, simply by
typing ipkg install cherokee-admin it went smooth, almost.. :)
I have some questions that I hope you can answer!
#1
I don't understand why the adminpage says
"Server status
Server is not running. "
It seems its active because I can access all my php scripts on the webserver
from a browser etc.. uhhm.. when I type cherokee in my linux terminal I get:
# cherokeeserver.c:715: Can't bind() socket (port=8008, UID=0, GID=0)
Do you know what I need to get it active in the admin page?
#2
I really want it to be a secure server, so that nobody but those who know the
password can access the webserver from remote locations.
I saw the Mysql authentication but i dont know what to type in the SQL Query.
so far I have typed in :
host : localhostport : 3306Unix Socket : /opt/bin/mysqlDB user : rootdb
password: passdatabase : authSQL Query : ??
in the auth database there is a table for user and password.
But it would be a big help if you could provide information how to design the
auth database and what I should write in the SQL query.. or maybe if you could
direct me to a guide for setting it up.. thank you so far !
I'm running Cherokee 0.7.2 on the wonderful NSLU2 box which is unslunged.
Best Regards,
Viktor K.
> From: [EMAIL PROTECTED]> Subject: Cherokee Digest, Vol 1, Issue 10> To:
> [email protected]> Date: Thu, 31 Jul 2008 12:00:03 +0200> > Send
> Cherokee mailing list submissions to> [email protected]> > 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> [EMAIL PROTECTED]> > You can reach the person
> managing the list at> [EMAIL PROTECTED]> > When replying, please edit your
> Subject line so it is more specific> than "Re: Contents of Cherokee
> digest..."> > > Today's Topics:> > 1. Authentication (Viktor S. Kristensen)>
> 2. Re: Authentication (Taher Shihadeh)> 3. Feedback: Improving the quality of
> Cherokee's documentation> (Taher Shihadeh)> 4. Re: [Cherokee-dev] Feedback:
> Improving the quality of> Cherokee's documentation (Alvaro Lopez Ortega)> 5.
> Re: [Cherokee-dev] Feedback: Improving the quality of> Cherokee's
> documentation (Stefan de Konink)> > >
> ----------------------------------------------------------------------> >
> Message: 1> Date: Thu, 31 Jul 2008 09:25:03 +0200> From: "Viktor S.
> Kristensen" <[EMAIL PROTECTED]>> Subject: [Cherokee] Authentication> To:
> <[email protected]>> Message-ID: <[EMAIL PROTECTED]>> Content-Type:
> text/plain; charset="iso-8859-1"> > Hi guys and thank you for this awesome
> light-end webserver!> > I have a NSLU2 box which has been
> unslung(http://www.nslu2-linux.org/) to 6.10. when I run the command in the
> linux terminal: ipkg install cherokee - every thing is fine and I can see the
> start page. (localhost:8008/> > But my intention is to make a private
> webserver and I was wondering how to add some security along the road. > >
> Like, for accessing every file on the server, you need a special password.> >
> I read somewhere that it was located at>
> /opt/etc/cherokee/sites-available/default> > but my folder is empty.. do you
> have any suggestions which can solve my problem. So I can password secure my
> files for uninvited guest? > > That would be a huge help.. thank you very
> much! and again, cherokee rocks!> > Best regards,> Viktor K. >
> _________________________________________________________________> News,
> entertainment and everything you care about at Live.com. Get it now!>
> http://www.live.com/getstarted.aspx> -------------- next part -------------->
> An HTML attachment was scrubbed...> URL:
> http://lists.octality.com/pipermail/cherokee/attachments/20080731/798af591/attachment.html
> > > ------------------------------> > Message: 2> Date: Thu, 31 Jul 2008
> 10:13:45 +0200> From: Taher Shihadeh <[EMAIL PROTECTED]>> Subject: Re:
> [Cherokee] Authentication> To: [email protected]> Message-ID:
> <[EMAIL PROTECTED]>> Content-Type: text/plain; charset="windows-1252"> > Hi
> there!> That 'sites-available' directory is for releases prior to 0.6.
> Cherokee stable is 0.7.2 and we're hoping to release 0.8 (much better, btw)
> really soon.> > You should use a current release. I'm unsure if you are
> running Python in the NSLU2, which is needed to launch cherokee-admin. If
> not, you can simply configure the server on your computer with a similar
> setup and then copy the resulting cherokee.conf file to whatever location you
> have defined for your compilation (parameter --sysconfdir).> > To password
> secure you only have to make sure that your rules are defined as non-final,
> and define a las rule (in this case with the 'final' flag enabled) that is
> authenticated by whatever mechanism your platform supports.> > This would be
> done from 'VirtualServers'-->[choose the one you've got defined; 'default' as
> default]-->Behaviour> And once you're in the final rule, use the 'Security'
> tab to define the mechanism (plain, PAM or whatever).> > I hope this is of
> use to you.> Kind regards,> Taher Shihadeh> > On Thursday 31 July 2008
> 09:25:03, Viktor S. Kristensen wrote:> > Hi guys and thank you for this
> awesome light-end webserver!> > > > I have a NSLU2 box which has been
> unslung(http://www.nslu2-linux.org/) to 6.10. when I run the command in the
> linux terminal: ipkg install cherokee - every thing is fine and I can see the
> start page. (localhost:8008/> > > > But my intention is to make a private
> webserver and I was wondering how to add some security along the road. > > >
> > Like, for accessing every file on the server, you need a special password.>
> > > > I read somewhere that it was located at> >
> /opt/etc/cherokee/sites-available/default> > > > > but my folder is empty..
> do you have any suggestions which can solve my problem. So I can password
> secure my files for uninvited guest? > > > > That would be a huge help..
> thank you very much! and again, cherokee rocks!> > > > Best regards,> >
> Viktor K. > -- > [EMAIL PROTECTED]> http://unixwars.com> > >
> ------------------------------> > Message: 3> Date: Thu, 31 Jul 2008 11:41:50
> +0200> From: Taher Shihadeh <[EMAIL PROTECTED]>> Subject: [Cherokee]
> Feedback: Improving the quality of Cherokee's> documentation> To: [EMAIL
> PROTECTED]> Cc: [email protected]> Message-ID: <[EMAIL PROTECTED]>>
> Content-Type: text/plain; charset="utf-8"> > Hello everyone.> This is an
> enhancement that has been needed for a long time. I post this on both lists
> because, even if it is an issue to be dealt with within the list for
> development, it affects every user (developer or not). I would appreciate if
> every response or contribution to this thread was sent exclusively to the
> normal Cherokee support list, so that we could keep this somehow
> centralized.> > As stated in
> http://code.google.com/p/cherokee/issues/detail?id=80 , the documentation is
> far better than it used to be, but we should design a master plan with clear
> milestones of what we need to make everyone happy with the docs available.> >
> Every little piece of advice and feedback is more than welcome. It would be
> great if we could do something about this for the upcoming 0.8 release, but
> this is definitely something that will need constant work (for this and all
> future releases).> > Needs:> ----------> * [1] Improve the navigability of
> the documentation.> * [2] Define a convenient hierarchical structure,
> generate a TOC, etc. > Currently the structure reflects more the internal
> architecture of > Cherokee rather than a traditional manual.> * [3] Integrate
> the current docs into the new tree.> * [4] Define and document a series of
> typical configuration tasks.> > Tasks to be documented:>
> -------------------------------------> * [1] How to configure virtual hosts
> from beginning to end, step by step.> * [2] How to tune scalability (IO cache
> & file, number of threads...)> * [3] How to setup authenticated resources> >
> Actual Structure:> ------------------------> Currently there is a way to
> generate a combined documentation with a TOC,> but navigability is less than
> optimal. A combined.html file can be created> using Asciidoc with the
> doc/build/build_combined.sh script, but internal > navigability is less than
> optimal. There might be a way to fix this other> than combining the whole
> documentation into a unique TXT file for Asciidoc> to process. The mentioned
> script creates the following Table of Contents:> > 1. Download> 2. Cherokee
> Documentation> 2.1. Compiling and Installing> 2.2. Configuration Interface>
> 2.3. General configuration> 2.4. Virtual Servers> 2.5. Encoders> 2.6. Icons>
> 2.7. Advanced topics> 2.8. Other advanced topics> 2.9. Internal configuration
> system> 3. Compiling and installing on Unix> 3.1. Required> 3.2. Optional>
> 3.3. Quickstart> 3.4. Advanced parameters> 3.5. Autostart> 4. Cherokee Admin>
> 5. General Configuration> 5.1. Binding> 5.2. IPv6 support> 5.3. Timeout> 5.4.
> KeepAlive> 5.5. Server Tokens> 5.6. Execution User and Group> 6. Virtual
> Server> 6.1. Add a new Virtual Server> 6.2. Basics> 6.3. Domain names> 6.4.
> Behavior> 6.5. Error Handler> 6.6. Logging> 6.7. Security> 7. Authentication>
> 7.1. Htpasswd Validator> 7.1.1. Parameters> 7.1.2. Compatibility> 7.1.3.
> Example> 7.2. Htdigest Validator> 7.2.1. Parameters> 7.2.2. Compatibility>
> 7.2.3. Example> 7.3. Mysql Validator> 7.3.1. Parameters> 7.3.2.
> Compatibility> 7.3.3. Example> 7.4. Pam Validator> 7.4.1. Parameters> 7.4.2.
> Compatibility> 7.4.3. Example> 7.5. Plain Validator> 7.5.1. Syntax> 7.5.2.
> Parameters> 7.5.3. Compatibility> 7.5.4. Example> 8. Virtual Server Rule>
> 8.1. OnlySecure> 8.2. Allow From> 8.3. Examples> 8.4. Authentication> 9.
> Icons> 10. Advanced Configuration> 11. Debugging Cherokee> 12. How to cross
> compile Cherokee> 12.1. Cherokee-Win32 from Linux> 12.2. Cherokee-Win32 from
> OS X> 13. How to generate SSL keys> 13.1. Locate CA.pl or CA.sh> 13.2. Create
> a new CA> 13.3. Generate a certificate request> 13.4. Sign the certificate
> request> 13.5. Self signed certificates> 13. Cherokee Tweak> 14. Internal
> Configuration> 14.1. Introduction> 14.2. Server> 14.3. Server Encoders> 14.4.
> Virtual Server> 14.5. Defining a virtual server behavior> 14.6. Logs> 14.7.
> Inclusion of Configuration> 15. Loggers> 15.1. Combined> 15.2. NCSA> 15.3.
> W3C> 16. Handler: CGI> 16.1. Parameters> 16.2. Examples> 17. Handler: List &
> Send> 17.1. Parameters> 17.2. Examples> 18. Handler: Directory Listing> 18.1.
> Parameters> 18.2. Examples> 19. Handler: FastCGI> 19.1. Parameters> 19.2.
> Examples> 19.3. Configuring PHP> 19.4. Note for developers> 20. Handler: File
> sending> 20.1. Parameters> 20.2. Examples> 21. Handler: Redirections> 21.1.
> Parameters> 21.2. Examples> 22. Handler: SCGI> 23. Balancer: Round Robin> 24.
> Enconder: Gzip> > Future structure:> ------------------------> To be
> determined. Navigability strategy must be drafted.> -- > [EMAIL PROTECTED]>
> http://unixwars.com> > > ------------------------------> > Message: 4> Date:
> Thu, 31 Jul 2008 11:54:02 +0200> From: Alvaro Lopez Ortega <[EMAIL
> PROTECTED]>> Subject: Re: [Cherokee] [Cherokee-dev] Feedback: Improving the
> quality> of Cherokee's documentation> To: [EMAIL PROTECTED]> Cc: [EMAIL
> PROTECTED], [email protected]> Message-ID: <[EMAIL PROTECTED]>>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes> > On 31
> Jul 2008, at 11:41, Taher Shihadeh wrote:> > > Tasks to be documented:> >
> -------------------------------------> > * [1] How to configure virtual hosts
> from beginning to end, step by > > step.> > * [2] How to tune scalability (IO
> cache & file, number of threads...)> > * [3] How to setup authenticated
> resources> > > I would add:> > * How to configure the most spread apps
> servers (php, django, RoR,..)> * How to manage logs> * How to manage security
> (SSL/TLS, certs, etc)> > BTW, it is grand to see that we are finally facing
> this issue! :-)> > --> Greetings, alo.> http://www.alobbs.com/> > > >
> ------------------------------> > Message: 5> Date: Thu, 31 Jul 2008 11:56:51
> +0200 (CEST)> From: Stefan de Konink <[EMAIL PROTECTED]>> Subject: Re:
> [Cherokee] [Cherokee-dev] Feedback: Improving the quality> of Cherokee's
> documentation> To: Alvaro Lopez Ortega <[EMAIL PROTECTED]>> Cc: [EMAIL
> PROTECTED], [email protected]> Message-ID: <[EMAIL PROTECTED]>>
> Content-Type: TEXT/PLAIN; charset=US-ASCII> > On Thu, 31 Jul 2008, Alvaro
> Lopez Ortega wrote:> > > On 31 Jul 2008, at 11:41, Taher Shihadeh wrote:> >>
> > > Tasks to be documented:> > > -------------------------------------> > > *
> [1] How to configure virtual hosts from beginning to end, step by> > > step.>
> > > * [2] How to tune scalability (IO cache & file, number of threads...)> >
> > * [3] How to setup authenticated resources> >> >> > I would add:> >> > *
> How to configure the most spread apps servers (php, django, RoR,..)> > * How
> to manage logs> > * How to manage security (SSL/TLS, certs, etc)> > My 2ct:>
> > * Development docs; example handlers *fully* documented.> * Adding
> documentation [in some sort standard] to the headerfiles.> > > Stefan> > > >
> ------------------------------> >
> _______________________________________________> Cherokee mailing list>
> [email protected]> http://lists.octality.com/listinfo/cherokee> > >
> End of Cherokee Digest, Vol 1, Issue 10>
> ***************************************
_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces.
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
