Skip to content
Projects

lichuang/replited has 252 GitHub stars and 11 forks. GitHot measured 0 stars in 24 hours and 0 in 7 days. Last checked 2026-11-15 13:52 UTC. Last push 2025-10-09.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
0
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Replicate SQLite to every where(S3\ftp\webdav\google drive\dropbox,etc)

Data

README.md

Original

replited(Replicate SQLITE Daemon)

GitHub stars GitHub forks

Introduction

Inspired by Litestream, with the power of Rust and OpenDAL, replited target to replicate sqlite to everywhere(file system,s3,ftp,google drive,dropbox,etc).

Why replited

  • Using sqlite's WAL mechanism, instead of backing up full data every time, do incremental backup of data to reduce the amount of synchronised data;
  • Support for multiple types of storage backends,such as s3,gcs,ftp,local file system,etc.

Support Backend

Type Services
Standard Storage Protocols ftpCI
Object Storage Services azblob gcs
s3CI
File Storage Services fsCI

Quick Start

Start a daemon to replicate sqlite:

replited --config {config file} replicate 

Restore sqlite from backend:

replited --config {config file} restore --db {db in config file} --output {output sqlite db file path}

Config

See config.md

Sub commands

Replicate

repicate sub command will run a background process to replicate db to replicates in config periodically, example:

replited  --config ./etc/sample.toml  replicate

Restore

restore sub command will restore db from replicates in config, example:

replited  --config ./etc/sample.toml restore --db /Users/codedump/local/sqlite/test.db --output ./test.db

command options:

  • db: which db will be restore from config
  • output: which path will restored db saved

Stargazers over time

​