Changes between Initial Version and Version 6 of Ticket #2169


Ignore:
Timestamp:
03/23/2015 04:17:45 PM (5 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2169

    • Property Cc sebastian trev matze added
    • Property Owner set to sebastian
    • Property Ready set
    • Property Summary changed from Use the same logic in development and production to Unify development and production implementation of multiplexer
  • Ticket #2169 – Description

    initial v6  
    11=== Background === 
    2 We're currently using Flask for the sitescripts development server, and flup and WSGI in production. This is problematic, because things that work fine in development (e.g. responses are automatically encoded as utf-8) don't work in production. 
     2We're currently using Flask for the sitescripts development server, and  a raw WSGI app running as FastCGI via flup in production. This is problematic, because things that work fine in development (e.g. responses are automatically encoded as utf-8) don't work in production. 
    33 
    44=== What to change === 
    5 How I see it, we have two options: 
    6  
    7 1. We use Flask in production - apparently it's possible to use it with FastCGI. 
    8 2. We don't use Flask in development anymore, creating a simpler server more similar to our production environment instead. 
     5Unify the multiplexer implementation into a common WSGI app, used both in production and by the development server using `werkzeug.serving` if installed, falling back to `wsgiref.simple_server`.