Build a posts feature end to end

You ship one feature — posts — into the Publish story’s blog app: entity, service, PostsController, validation, Postgres, and an e2e test. No JWT, no GraphQL — that complexity lives in api and auth. Each page leaves you with code that compiles and a command you can run.

What you end up with

hello for the quick-start binary, apps/blog/ for the tutorial app, and a posts/ feature with HTTP only.

Directoryapps/blog/
- Cargo.toml
- Directorysrc/
  - main.rs
  - module.rs
- Directorytests/
  - Directorye2e/
    main.rs
Directorycrates/
- Directoryfeatures/
  - Directorysrc/
    Directoryposts/
    entity.rs
    service.rs
    module.rs
    mod.rs
    Directoryhttp/
    controller.rs
    module.rs
    mod.rs

Two curls against the running binary — no token:

$ curl -s -X POST http://localhost:3005/posts \
    -H 'Content-Type: application/json' \
    -d '{"title":"Hello","body":"World"}'
{"id":"018f…","title":"Hello","body":"World"}

$ curl -s http://localhost:3005/posts/018f…
{"id":"018f…","title":"Hello","body":"World"}

And a passing e2e suite:

$ nestrs run test e2e
         PASS [   …] blog::e2e posts_round_trip

What you should know going in

The tutorial assumes you’ve already followed Getting started — a workspace you scaffolded with nestrs new hello, the nestrs CLI installed, and nestrs run dev hello serving Hello World from crates/features/src/hello/. Page 1 adds apps/blog/ with nestrs new blog; everything after that happens in blog, not hello. If you cloned this repository to explore Publish, scaffold hello and blog in a separate workspace — they are not hosted here. Skim Fundamentals, Configuration, and HTTP so module, provider, and controller are familiar terms. docker is available for the Postgres step.

Rust 1.96+ is required. The database and testing pages need Postgres (nestrs run db up); earlier pages run without one.

The pages, in order

1. Scaffold the app nestrs new blog, nestrs run dev blog, 404 on / — then read what the CLI wrote.

2. Declare the entity The Post entity with SeaORM and #[expose].

3. See the security payoff Run the reference api: an admin, a masked member, a cross-tenant 403 — no handler check.

4. Expose over HTTP PostsController, the service, GET and POST /posts.

5. Persist through Postgres DatabaseModule, migrations, transactional writes.

6. Validate inputs Valid at the boundary, 400 on a bad body.

7. Test it end to end apps/blog/tests/e2e/main.rs against an EphemeralDatabase.

8. Authenticate and authorize Guards, AppAbility, Bind — build the access control you lived on step 3.

9. Mirror on GraphQL A UsersResolver over the same service, ability, and dataloader.

Going further

Scaffold the app — the next step: add apps/blog/ with nestrs new blog.
Publish — the reference workspace this tutorial builds toward.
Getting started — the workspace setup this tutorial assumes.