A single install self hosted file storage server.

cargo install esetres

# check version to verify installation
esetres -V

Run the init command and go through the setup process.

esetres init

esetres start

Returns a simple running status for the server.

Creates a new bucket.

Request Body:

{
	"name": "bucket_name"
}

This is configured for local only access. It will invalidate the token cache causing a refetch from the database. This will be hit when you mint or revoke tokens.

Gets the requested file from the requested bucket. Requests to private must be authorized.

Uploads the file to the requested bucket with the requested file name.

Request Body: File Content In Bytes

Deletes the file with the requested bucket and file name.

Step by step process for setting up the environment variables, running the migration and creating your first bucket.

esetres init

Welcome to esetres cli!
|
o Do you want us to generate the token secret? yes
|
✓ Generated token secret.
|
o Select your the ip: 172.31.144.1
|
o Enter the port: 8080
|
o Use https? no

TOKEN_SECRET="[hidden]"

IP="172.31.144.1"
PORT="8080"
HTTPS=0

o .env file Ok? yes
|
✓ Created .env file.
|
o Run sqlite migration? yes
|
✓ Ran sqlite migration.
|
o Create a bucket? yes
|
o Enter the bucket name: default
|
✓ Bucket [default] created.
|
✓ Completed initialization.

Starts the server.

esetres start

Listening at 127.0.0.1:3000...

esetres uses a local sqlite database to store the tokens. In the init function you can choose to run this automatically or you can run it yourself at any time with:

esetres migrate

You can create buckets from the api or by creating the folders yourself on the server. However the CLI enables some extra functionality.

Creates a new bucket and the required folders.

esetres buckets create my_bucket

Deletes the bucket and all contents.

esetres buckets delete my_bucket

Lists all the buckets and their last modified time.

esetres buckets list

Name      Modified
-----------------------------------------------
default | 2024-06-11 09:36:37.522380 -05:00
test    | 2024-06-11 09:44:01.888576100 -05:00

Tokens allow you to control access to the server. It uses jwt with the Bearer scheme meaning authorized routes require the authorization header.

Tokens are cached by the server for fast responses and when you create or delete tokens the cache will automatically be updated.

Creates a new token with specified scope and access.

Create

esetres tokens mint MY_TOKEN

New token (MY_TOKEN) created for scope (*).
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...

Set Scope

Scope allows you to limit the buckets a token has access to.

# default scope is "*"
esetres tokens mint MY_TOKEN --scope default

Set Access

Access allows you to limit the permissions a token has to create buckets, upload files, and read files.

# default access is "read"
esetres tokens mint MY_TOKEN --access write

Lists all existing tokens with the most recently created being at the top.

esetres tokens list

Name                        Scope     Access
----------------------------------------------
ANOTHER_REALLY_LONG_TOKEN | test    | full
NEW_TEST_TOKEN            | default | read
TEST_TOKEN                | *       | write

Deletes a token from the database.

esetres tokens revoke MY_TOKEN

Token revoked.

The mime types come from mime-db. When you first start the server it will grab the types from the db and store it on machine. You can always delete the mime-db.json file to refresh it.