||2 weeks ago|
|.gitignore||4 weeks ago|
|Dockerfile||2 weeks ago|
|README.md||2 weeks ago|
|auth_basic.go||4 weeks ago|
|auth_ldap.go||4 weeks ago|
|auth_s3.go||4 weeks ago|
|config.go||4 weeks ago|
|error.go||4 weeks ago|
|go.mod||4 weeks ago|
|go.sum||4 weeks ago|
|main.go||4 weeks ago|
|middleware.go||4 weeks ago|
|s3_file.go||4 weeks ago|
|s3_fs.go||2 weeks ago|
|s3_path.go||4 weeks ago|
|s3_stat.go||4 weeks ago|
|webdav.go||4 weeks ago|
This is a technical preview, use it a your own risk, expect bugs and missing features.
Bagage will be a service to access your documents everywhere.
Currently, it is only a WebDAV to S3 proxy. Later, it may propose a web interface and support synchronization with the Nextcloud client.
how it works
bagage exposes a webdav endpoint behind an HTTP basic auth.
Credentials provided through basic auth are used to authenticate on the LDAP server, then 2 keys
garage_s3_secret_key are fetched from the user's LDAP profile to authenticate against the S3 server.
For now, these entries must be manually/externally added to the LDAP server prior using the service.
bagage is configured through environment variables. You can get all the keys and their default values in the config.go file.
You need a S3 endpoint and a LDAP server running. Once you correctly set your environment variables, you can simply run it:
go run .
A simple dockerfile is proposed to build a binary if you want.