I use backuppc with lighttpd.
Try something like:
alias.url += ( "/backuppc" => "/var/www/backuppc" )
$HTTP["url"] =~ "/backuppc" {
index-file.names = ( "BackupPC_Admin.cgi" )
cgi.assign += ( ".cgi" => "" )
}
Of course you'll also want an auth.require of some sort.
I also made some slight modifications to the CGI and backend libs to support
FastCGI, so I have a persistent spawn-fcgi process that runs the BackupPC
interface. The problem you'll have with the above is the cgi will have to be
setuid backuppc. With the fcgi version, I run the external process as the
backuppc user directly.
Does it matter significantly? Probably not. But it makes me feel better by not
seeing 2934829341 apache processes taking lots of ram in my ps listing. Just a
preference thing.
-G
> -----Original Message-----
> From: Juergen Harms [mailto:Juergen.Harms AT unige DOT ch]
> Sent: Monday, January 19, 2009 2:04 AM
> To: General list for user discussion, questions and support
> Subject: Re: [BackupPC-users] Backuppc on Lighttpd
>
> You are right - basic workload is no problem at all - backuppc web
> transactions happen very rarely.
>
> I have backuppc already running on apache, but wanted to have
> lighttpd
> to get webdav in support of a local foxmarks server. Again,
> load is not
> a problem, but the foxmarks documentation is very insistent that - on
> the long run - foxmarks support will be better if webdav is used.
>
> It looks like webdav can also be run with apache, but after some
> googling I decided that documentation is much more solid for getting
> things done with lighttpd - and, having no experience whatever in
> playing around with http servers, I need good documentation.
> Now that I
> am through a first step in the learning curve, I have the impression
> that the perl configuration files for lighttpd are much more flexible
> and easy to set up than the httpd configuration files - the
> problem with
> starting a cgi server + loading all the style sheets in the same
> directory is the only exception. An alternative would have
> been to run
> httpd and lighttpd next to each other, but that would only
> have been a
> second choice in case of excessive difficulties with lighttpd.
>
> Concerning that problem, I have found a quite satisfactory
> workaround:
> rather than calling the server with a URL that points to the
> directory,
> I (.../backuppc), I used /backuppc/BackupPC_Admin.cgi as an
> URL and the
> problem goes away. The user does not see this slightly "ugly"
> URL - he
> uses a bookmark in his toolbar folder.
>
> So, fundamentally the problem has a satisfactory workaround, but -
> learning - the academic question rests: with lighttpd, can one use an
> alias that goes to the directory and have all style sheets
> that sit next
> to the cgi included?
>
> --------------------------------------------------------------
> ----------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users AT lists.sourceforge DOT net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
