Roadmap for the official Fastify Demo Project

[jean-michelet]

Prerequisites

• Wait for Create basic architecture #1 to be merged

Issue

These are preliminary ideas, I'm open to suggestions to refine or expand this list.

To-Do List

1. Add Rate Limiter

• Implement rate limiting on the server #6

2. Create a Simple Tasks API

• Change JWT auth for cookie session auth #10
• CRUD tasks operations #15
• Handle permissions #29
• Enable linking images to tasks to illustrate file management with Fastify #28
• Allow tasks to be downloaded in CSV format. #34

3. User API for Profile and Password Management

• Create endpoints to allow users to update their profile information and passwords. #36

4. Registration with email verification process

• Registration with email verification process #49

5. Building a frontend client with Fastify/Vite

• Create a React SPA using fastify/vite #20

### Tasks

[mcollina]

+1 Maybe can you convert it into a TODO list?

[jean-michelet]

My main objections would be that it's a bit simplistic, a bit far from the real applications that developers generally use and can identify to, and that there are already a lot of tutorials on the subject, but I have nothing more against it.

Why would you preferer a TODO list? Do you think we can achieve a complete demo with that? I forgot to mention that I would like to add permissions management.

[mcollina]

No I meant to make the tasks above a markdown todo list

[jean-michelet]

🤦

Lol, sorry, I will do it this week.

[climba03003]

I would probably handle the CLI part.
oclif seem to addressed to long staling problem of argument parsing.
So I don't need to use the custom Command and Parser.

[jean-michelet]

If you feel like doing it, that's fine. If not, let me know. I'm going to be pretty busy for the next two weeks so I think I'll prioritise the demo for now.

[jean-michelet]

Should we keep a JWT authentication?
I say that because I think it will increase the overall complexity of the application.
I think a basic cookie session auth is enough to connect a SPA with a monolithic API, and is a good default imho.
We can eventually launch a Redis instance to store sessions with high performances.

Wdyt?

[mcollina]

I think a basic cookie session auth is enough to connect a SPA with a monolithic API, and is a good default imho.
We can eventually launch a Redis instance to store sessions with high performances.

I would do a cookie session auth.

[jean-michelet]

Hi, sorry for the lack of contribution on this repo but my new job is quite challenging, I'm starting to adapt so I'll continue soon.

I've created a package today to manage entity workflows (e.g. draft, published, archived). Can I create a Fastify plugin to wrap it @mcollina? It could look great on this demo and improve developer experience.

Here's the repo with some explanations: https://github.com/jean-michelet/workflow

[jean-michelet]

I think I was a little too enthusiastic about building the frontend part.
Doing all the tasks in step 2 correctly is enough to show a lot of interesting functionality for a first release.

[jean-michelet]

I am not sure that @fastify/vite is ready to be included cleanly with typescript.
I think it would be weird to generate a SPA without using it.
Do you need help @galvez?

[galvez]

The more people working on @fastify/vite the merrier :)

@onlywei has made great strides with the TS setup.