Skip to main content

MeST

Multi-Repository Sync Tool

features

  • Automated synchronization between a local bare repository or multiple remote repositories directly, enabling seamless updates.
  • The synchronization process runs entirely in the background, ensuring that branches across all repositories remain consistently up-to-date.
  • Users only interact with the local bare repository, enjoying a smooth experience without noticeable network latency, making it seem as though they are working locally despite the syncing of multiple repositories.

Usage

  1. setup config for memest

The unique config file is ~/.config/memest/config.ini You can customize your own configurations, and here's an example:

[default]
; Repository synchronization check interval
loop_period=10
; Repository cache folder
cache=~/.local/gitcache

[example]
; the local bare repository
; If it does not exist, the system will automatically create it.
local=~/.local/rep/example.git
; List of all remote repositories
; The configuration format for each repository is as follows
;   [address]|[private key file] or [address]
remote=git@github.com:xxmawhu/example.git|~/.ssh/id_rsa,
       git@githuh.com:xxmawhu/another.git,
  1. start
memest start

Metadata

Release files for MeMeST 2024.4.10.110919

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

Built distribution (wheel)

Table of built distributions (wheels) for MeMeST 2024.4.10.110919
File Interpreter ABI Platform Actions
MeMeST-2024.4.10.110919-py3-none-any.whl Python 3 none any Details for MeMeST-2024.4.10.110919-py3-none-any.whl

Release files / MeMeST-2024.4.10.110919-py3-none-any.whl

Download URL MeMeST-2024.4.10.110919-py3-none-any.whl
Size 34.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
37e6f517e6cd2086b1facdf614a28e998a73f68825f8d4597b20b44ed6aec846
BLAKE2b-256 checksum
How to use checksums
619f541905d5e41984c5150d10a3e99c37b8f6e6640281c1d7c4d42c585fb28a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.9.12

Security for MeMeST 2024.4.10.110919

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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page