You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
:rocket: Powered by [Fiber](https://gofiber.io/) and [HTMX](https://htmx.org/)
11
+
10
12
## Features
11
13
12
14
- List all buckets in your account
@@ -29,28 +31,27 @@ The application can be configured with the following environment variables:
29
31
-`USE_SSL`: Whether your S3 server uses SSL or not (defaults to `true`)
30
32
-`SKIP_SSL_VERIFICATION`: Whether the HTTP client should skip SSL verification (defaults to `false`)
31
33
-`SIGNATURE_TYPE`: The signature type to be used (defaults to `V4`; valid values are `V2, V4, V4Streaming, Anonymous`)
32
-
-`PORT`: The port the s3manager app should listen on (defaults to `8080`)
34
+
-`PORT`: The port the `s3manager` app should listen on (defaults to `8080`)
33
35
-`ALLOW_DELETE`: Enable buttons to delete objects (defaults to `true`)
34
36
-`FORCE_DOWNLOAD`: Add response headers for object downloading instead of opening in a new tab (defaults to `true`)
35
37
-`LIST_RECURSIVE`: List all objects in buckets recursively (defaults to `false`)
36
38
-`USE_IAM`: Use IAM role instead of key pair (defaults to `false`)
37
39
-`IAM_ENDPOINT`: Endpoint for IAM role retrieving (Can be blank for AWS)
38
-
-`SSE_TYPE`: Specified server side encrpytion (defaults blank) Valid values can be `SSE`, `KMS`, `SSE-C` all others values don't enable the SSE
40
+
-`SSE_TYPE`: Specified server side encryption (defaults blank) Valid values can be `SSE`, `KMS`, `SSE-C` all others values don't enable the SSE
39
41
-`SSE_KEY`: The key needed for SSE method (only for `KMS` and `SSE-C`)
40
-
-`TIMEOUT`: The read and write timout in seconds (default to `600` - 10 minutes)
42
+
-`TIMEOUT`: The read and write timeout in seconds (default to `600` - 10 minutes)
41
43
42
-
### Build and Run Locally
44
+
### Run Locally
43
45
44
-
1. Run `make build`
45
-
1. Execute the created binary and visit <http://localhost:8080>
46
+
1. Run `make run`
46
47
47
48
### Run Container image
48
49
49
50
1. Run `docker run -p 8080:8080 -e 'ACCESS_KEY_ID=XXX' -e 'SECRET_ACCESS_KEY=xxx' cloudlena/s3manager`
50
51
51
52
### Deploy to Kubernetes
52
53
53
-
You can deploy s3manager to a Kubernetes cluster using the [Helm chart](https://github.com/sergeyshevch/s3manager-helm).
54
+
You can deploy `s3manager` to a Kubernetes cluster using the [Helm chart](https://github.com/sergeyshevch/s3manager-helm).
54
55
55
56
## Development
56
57
@@ -70,7 +71,7 @@ The image is available on [Docker Hub](https://hub.docker.com/r/cloudlena/s3mana
70
71
71
72
### Run Locally for Testing
72
73
73
-
There is an example [docker-compose.yml](https://github.com/cloudlena/s3manager/blob/master/docker-compose.yml) file that spins up an S3 service and the s3manager. You can try it by issuing the following command:
74
+
There is an example [docker-compose.yml](https://github.com/cloudlena/s3manager/blob/master/docker-compose.yml) file that spins up an S3 service and the `s3manager`. You can try it by issuing the following command:
0 commit comments