No description
Find a file
Caj Larsson 8cc8e6a464
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Woodpecker CI badge
2023-01-11 13:32:39 +08:00
dataswamp Formatting with gofmt 2022-06-04 17:17:26 +08:00
doc Added logo 2022-06-07 20:29:23 +08:00
infrastructure Formatting with gofmt 2022-06-04 17:17:26 +08:00
server Renaming SwampfileService -> DataSwampService 2022-05-16 16:05:33 +08:00
util Testing the events on namespace Service 2022-05-16 13:40:32 +08:00
.dockerignore Fix the dockerfile 2022-05-07 12:18:34 +08:00
.gitignore Fix the dockerfile 2022-05-07 12:18:34 +08:00
.woodpecker.yml Woodpecker CI 2023-01-11 13:30:11 +08:00
default.toml Separate admin port 2022-05-07 14:48:22 +08:00
Dockerfile Progress on the great event refactoring 2022-05-13 21:30:42 +08:00
go.mod Complete restructure of domain and infra layer 2022-05-03 08:04:46 +08:00
go.sum Complete restructure of domain and infra layer 2022-05-03 08:04:46 +08:00
main.go logger, implements #9 2022-05-04 22:49:42 +08:00
Readme.md Woodpecker CI badge 2023-01-11 13:32:39 +08:00
sqlc.yaml Use sqlc to generate typesafe repository tools 2022-05-06 21:01:38 +08:00

status-badge

Bog: The Dataswamp

Logo

Is the warehouse too strict? Maybe you don't know the schema yet. And you know your lake is already full with a bunch of stuff that should have been deleted long ago?

Maybe it's time for the dataswamp, just POST your data in and fetch it later, maybe. Either way it will be deleted eventually.

Don't worry about access credentials, the datasawmp does authorization without authentication the old school way: encryption. Pass a password when you create your data and if you pass the same when you retrieve it, you get the same bits back.