shimesu installation online

Publish files. Keep the cloud.

shimesu turns static files and directories into stable HTTPS project URLs inside your own AWS account.

A complete publish flow

$ shimesu publish ./pitch.html --yes

deployed  pitch
url       https://pitch.<your-domain>/

Install and operate.

01

Get the source and CLI

Clone the project, then install the single Rust binary.

git clone https://github.com/michidk/shimesu.git
cd shimesu
cargo install --path cli
02

Deploy the AWS stack

Provision the private bucket, project table, and CloudFront distribution. The CloudFront certificate must be issued in us-east-1.

aws cloudformation deploy \
  --template-file cli/templates/stack.yaml \
  --stack-name shimesu \
  --parameter-overrides \
    BaseDomain=static.example.com \
    CertificateArn=arn:aws:acm:us-east-1:ACCOUNT:certificate/ID \
  --region eu-central-1
03

Point the CLI at the stack

Create ~/.config/shimesu/config.toml with your regional stack name.

[installation]
stack_name = "shimesu"
region = "eu-central-1" # use your stack region
04

Publish and manage

A file becomes its project index. A directory keeps its safe relative tree.

shimesu status
shimesu publish ./dist --project demo --yes
shimesu project list --json
shimesu project inspect demo --json
shimesu project delete demo --yes

Built for people and agents.

Human output uses readable progress and confirmations. Automation gets stable JSON and explicit non-interactive controls.

shimesu project list --json
shimesu publish ./report --project weekly --yes --json
shimesu project delete weekly --yes

Small, private, and idle-friendly.

Private storageS3 blocks public access and accepts reads only through CloudFront OAC.
HTTPS at the edgeCloudFront and ACM serve the base domain and every project subdomain.
Typed metadataDynamoDB stores project identity and the current deployment receipt.
No server fleetThere are no always-on containers, instances, or application servers.