Douwe Runner
Run one douwe.com project locally:
uvx douwe cambrium
or:
pipx run douwe cambrium
A bare name like cambrium resolves to github.com/DOsinga/cambrium and caches
the clone under ~/.cache/douwe/projects/.
From the main douwe.com checkout, you can also run the development copy directly:
python projects/douwe_runner/douwe.py cambrium
Project references can be local or GitHub-backed:
python projects/douwe_runner/douwe.py cambrium
python projects/douwe_runner/douwe.py ./projects/cambrium
python projects/douwe_runner/douwe.py DOsinga/cambrium
python projects/douwe_runner/douwe.py https://github.com/DOsinga/cambrium
Inside the douwe.com checkout, a bare name like cambrium prefers
./projects/cambrium. Outside that checkout, it resolves to
github.com/DOsinga/<name>.
Useful options:
python projects/douwe_runner/douwe.py --list
python projects/douwe_runner/douwe.py list
python projects/douwe_runner/douwe.py cambrium --embed
python projects/douwe_runner/douwe.py cambrium --no-browser
python projects/douwe_runner/douwe.py cambrium --port 9000
python projects/douwe_runner/douwe.py cambrium --refresh
Installed-package equivalents work the same way:
douwe --list
douwe cambrium --port 9000
douwe cambrium --refresh
Douwe Runner is a small local server for standalone douwe.com projects. It
accepts a project directory, a DOsinga/<repo> reference, or a GitHub URL; when
needed it caches a shallow clone under ~/.cache/douwe/projects/.
Use douwe --list or douwe list to see standalone GitHub-backed projects from
douwe.com. The list comes from https://douwe.com/projects/index.json and skips
projects that do not publish a standalone repo yet.
Project templates are rendered with Jinja2 and served with Tornado. Existing
douwe.com project templates can keep using {{ static }} and {% static "..." %} asset references, which the runner maps to local project and shared static
directories.
GitHub-backed projects use the git command-line tool for cloning and
refreshing. The GitHub CLI (gh) is not required, and the runner does not call
the GitHub API. Local project paths do not require git.
Projects that require WebSockets still need the full Django/Channels site for now.
1 maintainer
Metadata
1 maintainer
Release files for douwe 0.1.5
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 | |
|---|---|---|---|---|
| douwe-0.1.5.tar.gz | 13.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| douwe-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.9 kB
Release files / douwe-0.1.5.tar.gz
| Download URL | douwe-0.1.5.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da31aba47e1a8759380f84eb3651c968e98f981ac18f49accf4a527ca81ca71c
|
|
BLAKE2b-256 checksum How to use checksums |
40bae37eb97f7fc2777170a2401400f532b256fa38a8d7e862afd3a213e8ea89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.2
|
Release files / douwe-0.1.5-py3-none-any.whl
| Download URL | douwe-0.1.5-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d9dd11f06da7838139ed1acf82d009f9562434111eef5448626178198241f85
|
|
BLAKE2b-256 checksum How to use checksums |
aa4f790800a7af170d6fd0f3beeac31d95c22d22d5225a81dce39d0676d7df84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.2
|
Security for douwe 0.1.5
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.
