Logbless
Logbless is a simple file-based real-time log viewer.
Installation
macos/linux
wget -qO- https://astral.sh/uv/install.sh | sh
uv venv --python 3.12
source .venv/bin/activate
uv pip install logbless
windows
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
uv venv --python 3.12
.venv\Scripts\activate
uv pip install logbless
Requirements
Your logs must follow the format:
_log_format = "%(asctime)s - [%(levelname)s] - %(name)s - (%(filename)s).%(funcName)s(%(lineno)d) - %(message)s"
Example with logging
import logging
_log_format = "%(asctime)s - [%(levelname)s] - %(name)s - (%(filename)s).%(funcName)s(%(lineno)d) - %(message)s"
logging.basicConfig(
level=logging.INFO, format=_log_format, encoding="utf-8", filename="app.log"
)
Example log entry:
2025-01-14 07:25:00,779 - [INFO] - aiogram.event - (dispatcher.py).feed_update(172) - Update id=126061252 by bot id=6101975097
Usage
-
Initialize the application:
Before starting the application, create a configuration file by running:
uv run logbless init
After executing the command, a file named
logbless_conf.yamlwill be created. You need to edit this file before running the application.Example of
logbless_conf.yaml:authentication: login: admin # Login for accessing the web interface password: admin # Password for accessing the web interface host: 127.0.0.1 # Host where the server will run log_filename: logs.log # Path to the log file to be viewed path: /logs # URL path for accessing logs port: 8070 # Port to start the server title: Logbless Log viewer # Title of the web page
Adjust the file according to your needs.
-
Run the application:
After editing the configuration file, start the application by running:
uv run logbless run
The application will start and be available at
http://127.0.0.1:8070(or another address if you modified thehostandportsettings).
Metadata
Release files for logbless 0.1.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 | Actions |
|---|---|---|---|---|
| logbless-0.1.4.tar.gz | 8.0 kB | Without provenance | Details for logbless-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logbless-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for logbless-0.1.4-py3-none-any.whl |
Total release size: 16.0 kB
Release files / logbless-0.1.4.tar.gz
| Download URL | logbless-0.1.4.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
091c0be4e1019358e68289250ab3008df2ca5301312df3c768bea5a24feb24a9
|
|
BLAKE2b-256 checksum How to use checksums |
f75dca49b504d3e4c637b4acd0f948c22e09b845dfdad0211b67b550880dee11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.4
|
Release files / logbless-0.1.4-py3-none-any.whl
| Download URL | logbless-0.1.4-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5f9c0b4a995b095bbd2085b5a8a5e48b4c3ee929eb0fd691642ee733f27c478
|
|
BLAKE2b-256 checksum How to use checksums |
ad2151dfef101d0e57ce5a40038236631160f3aadaed4d93e4484618a867f31f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.4
|
Security for logbless 0.1.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.