railyard
Local application development server
Features
Basic compatibility with Google App Engine app.yaml files
Basic compatibility with Google App Engine dispatch.yaml files
Support for static files
Use
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:
dispatch:
- 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
Options
-e, --entrypoint = ENTRYPOINT
Overrides the entrypoint defined in the input file(s) with the given ENTRYPOINT.
When input is a dispatch.yaml file, an ENTRYPOINT must be provided for each service defined in the dispatch.yaml file. The ENTRYPOINT overrides must be specified in the same order as the code:service definitions in dispatch.yaml file.
Development
Setup
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
Tests
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
1 maintainer
Metadata
1 maintainer
Release files for railyard 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| railyard-0.1.0.tar.gz | 25.7 kB | Without provenance | Details for railyard-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| railyard-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for railyard-0.1.0-py3-none-any.whl |
Total release size: 55.2 kB
Release files / railyard-0.1.0.tar.gz
| Download URL | railyard-0.1.0.tar.gz |
|---|---|
| Size | 25.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47d1985d752d744486fad5c874022e5d7c3c2e26f63415eaf3e9dce36b83d3e0
|
|
BLAKE2b-256 checksum How to use checksums |
254974e8cc33c798ab11d37662a4cb73211a73c85a010f674a7156cc65e535f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.2 pkginfo/1.4.2 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.37.0 CPython/3.7.5
|
Release files / railyard-0.1.0-py3-none-any.whl
| Download URL | railyard-0.1.0-py3-none-any.whl |
|---|---|
| Size | 29.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
691e496ab2f44b56172157ad01b96af32489fd9171ef8dbdc77de748858fd73e
|
|
BLAKE2b-256 checksum How to use checksums |
7503df3264dfc44f31921a7d60c254e6d48fc3421ac2c404b841f3d2e72d5465
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.2 pkginfo/1.4.2 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.37.0 CPython/3.7.5
|
Security for railyard 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
