caj
/
bog
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
47 Commits
1 Branch
6 Tags
273 KiB
Go 93.2%
HTML 4.6%
Dockerfile 2.2%
 
 
 
master
v0.1.0
v0.2.0
v0.3.0
v0.3.1
v0.4.0
v0.4.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '3e6855d429'
${ noResults }
Go to file
Caj Larsson 3e6855d429 More progress on event and gofmt 3 years ago
dataswamp More progress on event and gofmt 3 years ago
infrastructure More progress on event and gofmt 3 years ago
server More progress on event and gofmt 3 years ago
util More progress on event and gofmt 3 years ago
.dockerignore Fix the dockerfile 3 years ago
.gitignore Fix the dockerfile 3 years ago
Dockerfile Progress on the great event refactoring 3 years ago
Readme.md Complete restructure of domain and infra layer 3 years ago
default.toml Separate admin port 3 years ago
go.mod Complete restructure of domain and infra layer 3 years ago
go.sum Complete restructure of domain and infra layer 3 years ago
main.go logger, implements #9 3 years ago
sqlc.yaml Use sqlc to generate typesafe repository tools 3 years ago

Readme.md

Bog: The Dataswamp

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.