garage.git - S3-compatible object store for small self-hosted geo-distributed deployments

	Commit message (Collapse)	Author	Age	Files	Lines
*	Reorder imports.	Alex Auvolat	2020-04-18	1	-1/+2
\| \| \| \| \| \| \|	Trying to separate: 1. Stuff for handling the swarm of nodes and generic table data replication 2. Stuff for the object store core application: metadata tables and block management 3. Stuff for the S3 API
*	Remove proto.rs & move some definitions out of data.rs	Alex Auvolat	2020-04-18	1	-0/+1
\|
*	WIP	Alex Auvolat	2020-04-17	1	-0/+5
\| \| \| \| \| \|	TODOs: - ensure sync goes both way - finish sending blocks to other nodes when they need them before deleting
*	Table range deletion	Alex Auvolat	2020-04-17	1	-7/+7
\|
*	Small refactorings	Alex Auvolat	2020-04-12	1	-1/+1
\|
*	Trying to do TLS	Alex Auvolat	2020-04-12	1	-4/+2
\|
*	Refactor a bit	Alex Auvolat	2020-04-12	1	-7/+6
\|
*	Keep network status & ring in a tokio::sync::watch	Alex Auvolat	2020-04-11	1	-3/+8
\| \| \| \| \| \|	advantages - reads don't prevent preparing writes - can be followed from other parts of the system by cloning the receiver
*	table::insert_many, version_table::updated	Alex Auvolat	2020-04-11	1	-3/+18
\|
*	Add block ref table	Alex Auvolat	2020-04-10	1	-2/+2
\|
*	Fix the Sync issue. Details:	Alex Auvolat	2020-04-10	1	-4/+3
\| \| \| \| \| \| \|	So the HTTP client future of Hyper is not Sync, thus the stream that read blocks wasn't either. However Hyper's default Body type requires a stream to be Sync for wrap_stream. Solution: reimplement a custom HTTP body type.
*	Why is it not Sync??	Alex Auvolat	2020-04-09	1	-0/+71
\|
*	Some progress	Alex Auvolat	2020-04-09	1	-59/+0
\|
*	Reorganize table API	Alex Auvolat	2020-04-09	1	-18/+14
\|
*	Work & TODO	Alex Auvolat	2020-04-08	1	-2/+5
\|
*	Some work	Alex Auvolat	2020-04-08	1	-3/+4
\|
*	Some work in actually storing things	Alex Auvolat	2020-04-08	1	-0/+59