Skip to main content

Simple local application development server

Project description


Local application development server


  • Basic compatibility with Google App Engine app.yaml files

  • Basic compatibility with Google App Engine dispatch.yaml files

  • Support for static files


To run an application defined in a app.yaml file:

$ railyard app.yaml

To run an application which uses a dispatch.yaml file:

$ railyard dispatch.yaml

Railyard will first search the folder it is run from for the service definition files, failing that, it will search folders matching the service names. For example, take the following dispatch.yaml:

  - url: "*/app1/*"
    service: app1

  - url: "*/app2/*"
    service: app2

Railyard will use files in the following order:

  • ./app1.yaml

  • ./app1/app1.yaml

  • ./app2.yaml

  • ./app2/app2.yaml



It is recommended to develop using a pipenv.

A development environment can be set up automatically:

$ pipenv install --dev

You can work directly inside the development environment:

$ pipenv shell

From inside the development environment, you can install the pre-commit hooks using pre-commit:

$ pre-commit install

To run the pre-commit hooks manually:

$ pre-commit run --all-files


To run the unit tests:

$ python -m unittest

The pre-commit tests are run using coverage. To see where the coverage tests are failing:

$ coverage report -m

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

railyard-0.0.3.tar.gz (23.4 kB view hashes)

Uploaded source

Built Distribution

railyard-0.0.3-py3-none-any.whl (27.5 kB view hashes)

Uploaded py3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page