Microblog server
Python backend for a low-volume personal microblog.
Input server (Telegram bot) waits for user to post new microblog entries and saves them to storage (git repo). Entries can be fetched from storage via provided Python library. There is also a plugin for Pelican to render microblog entries on a static web site.
Input server and storage engine should be easy to replace or add new implementations in future.
Installation
-
Python package is published at PyPI: https://pypi.org/project/microblog-server/
- Install with
pip install microblog-server - Make sure that
gitis available in $PATH
- Install with
-
Ready to go Docker image is also available
Usage
Running input server
- Commandline entrypoint:
microblog - Configuration is done via environment variables:
MICROBLOG_STORAGE: Path to a local checkout of git repository that stores the microblogMICROBLOG_TOKEN: Telegram bot tokenMICROBLOG_USERS: Comma-separated list of Telegram accounts allowed to interact with the bot
Using Python library to read microblog from storage
See the source code
Rendering static web site
See Pelican docs for general information on using static site generator.
Plugin configuration:
# pelicanconf.py
import microblog.pelican
import microblog.storage
PLUGINS = [
microblog.pelican,
]
MICROBLOG = microblog.storage.GitStorage('./path/to/local/copy/of/git/repo/')
Your theme is expected to provide the following templates:
Check plugin source for further information. See author's site configuration for further examples.
License and copyright
Copyright 2022 Vitaly Potyarkin
Licensed 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.
Metadata
Release files for microblog-server 1.0.4
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 | |
|---|---|---|---|---|
| microblog-server-1.0.4.tar.gz | 17.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| microblog_server-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.5 kB
Release files / microblog-server-1.0.4.tar.gz
| Download URL | microblog-server-1.0.4.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d6ac0369a91c9e140099cf69769cfc8fe29c52fa0c6afe5bfac68406415b919
|
|
BLAKE2b-256 checksum How to use checksums |
5d4eb789add2459dd0bc1d312afe785b737f7b5820fabfa11ff1842177ab51db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.7
|
Release files / microblog_server-1.0.4-py3-none-any.whl
| Download URL | microblog_server-1.0.4-py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ff71e8b13028470ec63365aae83992249c50e93d8714219d0ec7791efda4e6d
|
|
BLAKE2b-256 checksum How to use checksums |
634c5a9700d125efb1c3d1026b124eaac59771949eaa00c72a9d199edc651de0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.7
|
Security for microblog-server 1.0.4
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.