Closed Bug 655318 Opened 13 years ago Closed 13 years ago

README is lacking info howto setup lighttpd/fcgi/flup/python-weave server

Categories

(Cloud Services :: Server: Other, enhancement)

x86
Linux
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: marcel, Assigned: tarek)

Details

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: 

The following is a small mini-howto for inclusion in the readme:

1. Make sure you have the following packeages installed: flup, virtualenv, mercurial:
With gento use: emerge -avuDN flup virtualenv mercurial

2. Unpack the server-full python version lets say under /usr/src/weave-full

3. make build ; /usr/src/weave-full/bin/easy_install flup

4. I had to edit the Makefile to take out the memcache dependency. YMMV.

5. Edit development.ini:
[server:main]
use = egg:Flup#fcgi_thread
host = 0.0.0.0
port = 5000

6. Edit conf/sync.ini:
[storage]
backend = sql
sqluri = sqlite:////usr//src//weave-full//weave_storage
standard_collections = false

[auth]
backend = sql
sqluri = sqlite:////usr//src/weave-full//weave_user
pool_size = 100
pool_recycle = 3600
create_tables = true
fallback_node = https://www.yourserver.net/yourpath/

7. Edit your lighttpd.conf:
server.modules   += ( "mod_fastcgi" )
fastcgi.server    = ( 	"/yourpath" => ((
                   		"host" => "127.0.0.1",
		                "port" => 5000,
				"idle-imeout" => 32,
				"check-local" => "disable",
				"disable-time" => 1,
				"fix-root-scriptname" => "enable"
				))
		     )
8. Start the python module
/usr/src/waeve-full/paster serve /usr/src/weave-full/development.ini --daemon

9. Restart your lighttpd:
/etc/init.d/lighttpd restart

Reproducible: Always


Actual Results:  
Running lighttpd/fcgi/python-weave
Assignee: nobody → tarek
Thanks for the help, Tarek!
Pushed at https://hg.mozilla.org/services/server-full/rev/3e4e61e7bc7b

thanks for your contribution and happy hacking
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.