openwrite is a minimalist blogging platform built for writing freely, hosting independently, and publishing without noise.
Features
- Multiple blogs per user(limit defined in .env)
- Single-blog mode
- Supports sqlite and mysql databases
- Upload images to local storage or bunny cdn
- Drafts
- Simple markdown editor in posting
- Discover section
- Privacy:
- Set if blog should be indexed in search engines
- Set if post should be listed in "Discover" section
- Set if username should appear in post page (anonymous posts)
- Lightweight
- No tracking, only data collected is anonymized(hashed) IP for post view counting and likes
- Custom CSS per blog
- Federation using ActivityPub protocol
- Likes system
- Posts importing from xml/csv
- Blog themes
- Gemini protocol
- Statistics per post
- Multilanguage (currently English and Polish)
- Custom favicon per blog
- Subpages per blog
- Valkey support
- Post tags, filtering
- Optional comments per post
- Auto save during typing
Installation
- To install openwrite, clone it with
pip:
pip install openwrite
- Then run:
openwrite init
- Answer few questions about your instance to generate .env and create all necessary directories.
- Run:
openwrite run
to run it in foreground or:
openwrite run -d
to run it in background.
- Default user is
adminwith passwordopenwrite. You can (and should!) change it in your dashboard. Enjoy!
Local development over HTTP
For http://localhost:8081, set these values in .env:
DOMAIN=localhost:8081
IP=127.0.0.1
PORT=8081
GEMINI=no
When working from a checkout, install it with ./venv/bin/python -m pip install -e .
so changes in this folder are used by the CLI.
Run ./venv/bin/openwrite debugrun (or ./venv/bin/openwrite run) and open
http://localhost:8081. DOMAIN must match the hostname and port in the browser,
without a protocol prefix. For a custom local hostname such as openwrite.local,
use DOMAIN=openwrite.local:8081 and point that hostname to 127.0.0.1 in your hosts file.
Restart the server after changing .env.
Both commands serve plain HTTP. In an HTTPS deployment, terminate TLS at a reverse
proxy and forward the original host and scheme with X-Forwarded-Host and
X-Forwarded-Proto so browser links use the public address.
Metadata
Release files for openwrite 0.17.1
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 |
|---|---|---|---|---|
| openwrite-0.17.1.tar.gz | 1.3 MB | Without provenance | Details for openwrite-0.17.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openwrite-0.17.1-py3-none-any.whl | Python 3 | none | any | Details for openwrite-0.17.1-py3-none-any.whl |
Total release size: 2.7 MB
Release files / openwrite-0.17.1.tar.gz
| Download URL | openwrite-0.17.1.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aeba327d1257360ebabbd7848b8a6b283a07bb49cb68aaf156005a36c127351a
|
|
BLAKE2b-256 checksum How to use checksums |
a1345c841e48d47c5570f03885dd56051b60676fa7f1f1c6535ea5c0ac006666
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Release files / openwrite-0.17.1-py3-none-any.whl
| Download URL | openwrite-0.17.1-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc431fe13388440cbe89e44617c39318b27075f742a9708b9482c002ee8a60df
|
|
BLAKE2b-256 checksum How to use checksums |
26c964bd3f75bcfb4fc2816ae6aacb36af91522cdaa3c7e53165fe63be5487be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Security for openwrite 0.17.1
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.