dudeswave2

Commit Graph

Author	SHA1	Message	Date
absc	5f14a4f6cb	Start to split the back-end further in more minor processes. The back-end will expose only the public APIs to be consumed by the listeners. The new users server takes care of the users management. Other subsystems will follow (i.e. GUI, fedi, blog etc..).	2024-09-15 12:14:29 +00:00
absc	eebf62d527	Split the web front-end and the backend into separate applications. This design will make things easier to both scale and test. Having a dedicated back-end application allow us to keep the API stable, while improving the internals.	2024-09-10 19:40:30 +00:00
absc	31da1067da	Add the backend app. Better to split the main functions in it's separate application. This will be used by all the other part of the dudeswave experience.	2024-09-09 20:14:18 +00:00

Author

SHA1

Message

Date

absc

5f14a4f6cb

Start to split the back-end further in more minor processes.

The back-end will expose only the public APIs to be consumed
by the listeners. The new users server takes care of the users
management.

Other subsystems will follow (i.e. GUI, fedi, blog etc..).

2024-09-15 12:14:29 +00:00

absc

eebf62d527

Split the web front-end and the backend into separate applications.

This design will make things easier to both scale and test.
Having a dedicated back-end application allow us to keep the API
stable, while improving the internals.

2024-09-10 19:40:30 +00:00

absc

31da1067da

Add the backend app.

Better to split the main functions in it's separate application.
This will be used by all the other part of the dudeswave
experience.

2024-09-09 20:14:18 +00:00

3 Commits (c3731bf0f31a6f40edb7d9fee4c6b4cde77b26c9)