-
Notifications
You must be signed in to change notification settings - Fork 37
use uwsgi instead of paste #471
base: develop
Are you sure you want to change the base?
Conversation
Conflicts: CHANGES.txt
|
||
# remove exiting links | ||
rm ${:prefix}/bin/python | ||
for i in $(ls ${:prefix}/bin/*[23].*); do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks really unstable. Why do we need to remove the files in the first place? And why can't we match python*
here?
For me, this fails with:
which is curious, since both my system Python and the adhocracy Python have zlib installed. |
recipe = collective.recipe.template | ||
output = ${buildout:bin-directory}/uwsgi | ||
input = inline: | ||
#!/bin/bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be /bin/sh
- the file is not dependent on bash at all, or is it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be /bin/sh - the file is not dependent on bash at all, or is it?
its not working with sh.
When I install multiple times (just run |
@phihag: Can you try to run |
ln -vfs ${buildout:directory}/python-2.7/bin/python2.7 $DEST; | ||
update-command = ${:command} | ||
# Symlink include, lib directory, uwsgi needs this there | ||
ln -s ${buildout:directory}/python-2.7/include ${:prefix}/include |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also pass in the -f
and -T
options here, since we're symlinking a directory. In fact, is that the rationale for the rm
s above? If so, just adding -fT
and removing the rm
s will suffice.
With the changes, uwsgi starts and serves the correct page, but still mentions
This looks like one of the options we set isn't actually boolean. |
############################################################################## | ||
|
||
[domains] | ||
uwsgi = 127.0.0.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these two entries used anywhere? It seems like we're simply using {main:port}
(as we should)
@@ -7,8 +7,6 @@ | |||
############################################################## | |||
|
|||
[DEFAULT] | |||
{% if parts.adhocracy.debug == 'True' %}debug = True {% end %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is this related to uwsgi?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This debug flag does not work with mutliprocess WSGI-servers such as uwsgi
Its better to use the domains/ports parts only for server hosts/ports settings and the adhocracy part for adhocracy configuration: * adhocracy.host is now domains.wsgi * port.main is now ports.wsgi * domains.main is no adhocracy.domain
touch-reload = true is throws: "unable to stat() true, events will be triggered as soon as the file is created"
fixed |
bin/uwsgi sets LD_LIBRARY_PATH now |
allow to extent the "LD_LIBRARY_PATH" |
ah :) |
Testet build.sh with Debian 7.1 netboot image, OK |
no, the recipe minitage.recipe.du was the reason, fixed. |
Can you try again or give me an VM to investigate this? |
@phihag do you still have problems? |
#444