Custom WSGI server not picked up by buildout

1

I have this instance configuration for WSGI server bjoern (could be any other WSGI server):

[instance1]
<= wsgi.py
debug-mode = off
control-script = instance1
http-address = 11001
zeo-address = 11000
eggs +=
    collective.sentry
    dataflake.wsgi.bjoern
wsgi-ini-template = ${buildout:directory}/templates/bjoern.ini.in

I see that dataflake.wsgi.bjoern has been added to the bin/instance1 script. But the wsgi.ini is still the waitress related configuration file....anything I am missing?

2

I've been using bjoern with a similar recipe for a while now, what's the content of your bjoern.ini.in template?

Mine starts with:

[server:main]
use = egg:dataflake.wsgi.bjoern#main
listen = %(http_address)s
reuse_port = False
...
3

What are the main advantages of bjorn over waitress for you that you choose bjoern?

4

The main purpose of my experiment was to make Waitress shut up with unwanted console messages :slight_smile:

5

PROS: faster, lighter, simpler, no problem in my environments so far
GitHub - jonashaag/bjoern: A screamingly fast Python 2/3 WSGI server written in C.
wsgi_filestream.md · GitHub
A Performance Analysis of Python WSGI Servers: Part 2 | Blog | AppDynamics

CONS: managed by a single developer ....

6

Bjørn, maybe ? :slight_smile:

7

Performance of WSGI servers in the context of Plone is likely irrelevant. The core performance of Plone is and remains slow...any WSGI server should be able to handle Plone.