Inspired by local memes
This is a learning project made to better understand python web frameworks and complex server setups. There will be multiple implementations of the basic interface, with using different database systems, as well different framework (python or maybe other in the future). These implementations will be united using a complex server setup.
Each implementation will be done in waves and tagged along the way for easier navigation. Each wave requires implementing a part of the basic interface. A wave will be described in full after any full (database + framework) implementation reaches the previous wave
- Basic Configuration
- Simplest Endpoint(s)
- X-Framework header for all requests
- Error handlers (404, 500)
- User & block-list data structures
- Classic authorization services
- Blocking user tokens for sign-out
- One protected resource (
/home/)
- Games & Participant tables (+cascades)
- Pagination with filters & sorts
- Participant listing for participants
- Updating & deleting for owners only
TBD
Codename A, because alchemy sounds fun
Codename M, the letter after N, as in noSQL
Codename E, because...
Codename F, the sixth letter from micro-Framework
Codename R, the sixth letter from the library name
Codename X, in honour of xi.effect
Codename B, because falcon is a Bird...
Codename P, because performance, I guess
- Tornado
- Pyramid
- Dash
- Django RF
- Node.js
Tags and dates per implementation per wave
| codename | wave1 | wave2 | wave3 | wave4 |
|---|---|---|---|---|
| A | w1a [26 Aug 2022] | w2a [30 Aug 2022] | ||
| M | ||||
| E | ||||
| F | w1f [30 Aug 2022] | w2f [30 Aug 2020] | ||
| R | ||||
| X | w1x [25 Aug 2022] | |||
| B | ||||
| P |
TBA