Skip to main content

Turn a directory into a git-based Blockchain

Project description

autoblockchainify — Turn a directory into a git-based Blockchain

git is probably the oldest and most widely used Blockchain with the largest user base and toolset, even though most people think of git as a source code control system. To learn more, see GitBlockchainTimestamping.md.

How does autoblockchainify work?

  • Frequently (default: every 10 minutes), the directory tree is checked for changes. If there are changes, they are commited to git and timestamped using Zeitgitter.
  • If no changes have been made in a larger period (default: 1 hour), a commit is forced and Zeitgitter-timestamped, as an immediate evidence of no changes.
  • If at the time of commit the last timestamp using the mail-based PGP Digital Timestamping Service is older than this larger period (again: 1 hour by default) and the mail interface has been configured, a timestamp will be requested there.
  • All timestamps requested from the Zeitgitter network will be regularily cross-timestamped within the Zeitgitter network and with the PGP Digital Timestamping Service as well as other (Blockchain-based) timestamping services.

What do I need to configure?

If you are happy with the default configuration, nothing. This default configuration includes:

  • A commit and Zeitgitter timestamp every 10 minutes, if there have been changes.
  • A commit and Zeitgitter timestamp every hour, even if there have been no changes.

If you would like to change the above intervals, or if you would like the following additional features, do change autoblockchainify.conf in the working directory or set the AUTOBLOCKCHAINIFY_* environment variables:

  • Additional, direct timestamping against the PGP Digital Timestamping Service by mail; or
  • Pushing to a remote repository for backup and/or publication purposes on every change. After changes to the configuration, you need to restart autoblockchainify (or the Docker container) to have changes picked up.

If you would like to exclude files from inclusion in the git repository (and therefore the Blockchain, the timestamps, and the remote repositories):

  • Modify .gitignore in the working directory.

How do I run it?

The preferred way is to run a Docker image using docker-compose and point the /blockchain directory to the directory you want be automatically archived to your Blockchain. See the files docker-compose.yml and sample.env.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

autoblockchainify-1.0.1.tar.gz (29.3 kB view details)

Uploaded Source

Built Distribution

autoblockchainify-1.0.1-py3-none-any.whl (30.2 kB view details)

Uploaded Python 3

File details

Details for the file autoblockchainify-1.0.1.tar.gz.

File metadata

  • Download URL: autoblockchainify-1.0.1.tar.gz
  • Upload date:
  • Size: 29.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.11.2

File hashes

Hashes for autoblockchainify-1.0.1.tar.gz
Algorithm Hash digest
SHA256 72deb4a4921a39c30da75ef37cec9a7cbd5593e846da56475bc80898478f4bb7
MD5 8cd872ae1083ccceb9b160413783a1d1
BLAKE2b-256 156d293af104e14f77f828a316a63158b197c566840976aa9d9c16c53b9e0853

See more details on using hashes here.

File details

Details for the file autoblockchainify-1.0.1-py3-none-any.whl.

File metadata

File hashes

Hashes for autoblockchainify-1.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 14f6642ec549a5411d6fd9266315e59a08e0fac0b32c9b9602e98770cc71ac23
MD5 9fa610900e155d04e1a67853f2ebf8a7
BLAKE2b-256 fdda049ba3c6a4b311b94a4660359cb7f63d35e2733d9e5c56d51168f65ba575

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page