blogodev

Presents an auto-recompiling front end to a Blogofile 0.7.1 site.

Just run:

blogodev -v

and you’ll get the functionality of “blogofile serve” combined with a modified Writer process that scans the source directory and rebuilds if any files change. Writes out to a temp directory and copies files back, deleting those that are no longer present.

Command line args are a tiny subset of that of Blogofile:

usage: blogodev [-h] [-s DIR] [-v] [-vv] [PORT] [IP_ADDR]

positional arguments:
  PORT                  TCP port to use
  IP_ADDR               IP address to bind to. Defaults to loopback only
                        (127.0.0.1). 0.0.0.0 binds to all network interfaces,
                        please be careful!

optional arguments:
  -h, --help            show this help message and exit
  -s DIR, --src-dir DIR
                        Your site's source directory (default is current
                        directory)
  -v, --verbose         Be verbose
  -vv, --veryverbose    Be extra verbose

Make sure that any scripts or filters in your Blogofile environment use bf.writer.output_dir to determine the destination of files, instead of hardcoding to _site.

Metadata

Release files for blogodev 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for blogodev 0.1.3
File	Size	Uploaded	Provenance
blogodev-0.1.3.tar.gz	5.9 kB	Jul 18, 2012	Without provenance	Details

Release files / blogodev-0.1.3.tar.gz

Download URL	blogodev-0.1.3.tar.gz
Size	5.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`8cfa435433f8a7d74d429b63d9da800eca7dd010a35cbede8791d9f31e3e567b`
BLAKE2b-256 checksum How to use checksums	`8f0a58c748732a10befe0eff505e28f829c67fd1276f28d04f723d0e65044060`
Upload date	Jul 18, 2012
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for blogodev 0.1.3

Report project as malware

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.