Smeltery
Get started

Getting started

v0.1

The app layout

text
my-app/
├── app/
│   ├── controllers/  models/  middleware/  providers/  services/
│   ├── commands/  jobs/  agents/  mail/  sparks/  helpers/
├── bootstrap/
│   ├── app.rs        wires the app: config, routes, middleware (the library root)
│   └── main.rs       the binary: hands the command line to smeltery::run
├── config/           typed config structs read from .env
├── routes/           web.rs (browser routes), api.rs (under /api)
├── database/         migrations/  seeders/  factories/  database.sqlite (SQLite apps)
├── resources/        views/ (pages, layouts/, components/, sparks/)  css/
├── public/           served as-is (assets/images, assets/css, assets/js)
├── storage/          app/public  app/private (the app's files)  framework (Smeltery's)  logs
├── tests/
├── .env  .env.example
├── CLAUDE.md  AGENTS.md
└── Cargo.toml

The app is one crate: bootstrap/app.rs is the library root and pulls each folder in as a module, so crate::app::controllers::home is app/controllers/home.rs. Every folder has a mod.rs.

storage/app/ holds only the app's own files (public/ is served at /storage after smeltery storage:link, private/ never is). storage/framework/ holds Smeltery's working files, created when first needed: cache/ (CACHE_STORE=file), sessions/ (SESSION_DRIVER=file), uploads/ and sparks/ (upload temp files). With --db sqlite the database is database/database.sqlite (?mode=rwc creates it on first connect). Git ignores the database file and everything under storage/.

↑↓ moveEnter openEsc close