Hi Alex, Don’t worry it is a switch and thus optional. This is also present in 1.7.1 and is actively used. The current state of master is a regression in that respect.
Bolke > On 14 Jan 2017, at 10:13, Alex Van Boxel <a...@vanboxel.be> wrote: > > Hey Bolke, I've missid this requirement: daemonizing the webserver?! Don't > do this by default. That would brake running on Kubernetes or in Docker. > Make it optional with a flag! > > On Fri, Jan 13, 2017 at 8:48 PM Bolke de Bruin <bdbr...@gmail.com > <mailto:bdbr...@gmail.com>> wrote: > >> Dear All, >> >> I have made Airflow 1.8.0 alpha 5 available at >> https://people.apache.org/~bolke/ <https://people.apache.org/~bolke/> >> <https://people.apache.org/~bolke/ <https://people.apache.org/~bolke/>> . >> Again no Apache release yet - this is for testing purposes. I consider this >> Alpha to be a Beta if not for the pending features. If the pending features >> are merged within a reasonable time frame (except for **, as no progress >> currently) then I am planning to mark the tarball as Beta and only allow >> bug fixes and (very) minor features. >> >> Blockers: >> * None >> >> Fixed issues >> * DAG.catchup : minor changes needed, documentation still required, >> integration tests seem to pass flawlessly >> * Respect retry_delay >> >> Pending features: >> * Cgroups + impersonation: clean up of patches on going, more tests and >> more elaborate documentation required. Integration tests not done yet >> >> Todo’s (Beta permitted): >> * set default log location for Childs correctly >> * fix systems scripts >> * daemonizing of webserver >> >> Almost there! >> Bolke > > -- > _/ > _/ Alex Van Boxel
