.. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at .. http://www.apache.org/licenses/LICENSE-2.0 .. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Running Airflow with upstart ============================ Airflow can integrate with upstart based systems. Upstart automatically starts all airflow services for which you have a corresponding ``*.conf`` file in ``/etc/init`` upon system boot. On failure, upstart automatically restarts the process (until it reaches re-spawn limit set in a ``*.conf`` file). You can find sample upstart job files in the ``scripts/upstart`` directory. The following assumptions have been used while creating these unit files: 1. Airflow will run as the following `user:group` ``airflow:airflow``. Change ``setuid`` and ``setgid`` appropriately in ``*.conf`` if airflow runs as a different user or group 2. These files have been tested on **Ubuntu 14.04 LTS** You may have to adjust ``start on`` and ``stop on`` stanzas to make it work on other upstart systems. Some of the possible options are listed in ``scripts/upstart/README`` Modify ``*.conf`` files as needed and copy to ``/etc/init`` directory. You can use ``initctl`` to manually start, stop, view status of the airflow process that has been integrated with upstart .. code-block:: bash initctl airflow-webserver status