this repo has no description
notes: deprecate todo's
+1
-53
+1
notes/Todo's.md
+1
notes/Todo's.md
···
1
+
Todo's from these notes are deprecated and replaced by Issues on the codeberg repo.
-21
notes/Todo's/Client.md
-21
notes/Todo's/Client.md
notes/Todo's/Cross-instance API's.md
notes/Todo's/Cross-instance API's.md
This is a binary file and will not be displayed.
notes/Todo's/Server-client API's.md
notes/Todo's/Server-client API's.md
This is a binary file and will not be displayed.
-23
notes/Todo's/Server.md
-23
notes/Todo's/Server.md
···
1
-
---
2
-
kanban-plugin: board
3
-
---
4
-
5
-
## New
6
-
7
-
## On wait
8
-
9
-
## Todo
10
-
11
-
## Started
12
-
13
-
## Completed
14
-
15
-
- [ ] [[1 - Deprecate SQLite, continue with only Postgres, further solidifying Podman as a development tool for Lumina]]
16
-
17
-
%% kanban:settings
18
-
19
-
```
20
-
{"kanban-plugin":"board","list-collapse":[false,false,false,false,false]}
21
-
```
22
-
23
-
%%
-9
notes/Todo's/Server/1 - Deprecate SQLite, continue with only Postgres, further solidifying Podman as a development tool for Lumina.md
-9
notes/Todo's/Server/1 - Deprecate SQLite, continue with only Postgres, further solidifying Podman as a development tool for Lumina.md
···
1
-
✅ Implemented in PR [#2](https://git.strawmelonjuice.com/strawmelonjuice/Lumina/pulls/2)
2
-
In the past, I've worked with mostly SQLite because it made development easy. Since the introduction of Redis as cache,
3
-
Podman is always somehow involved in the development run, be it to provide the entire environment or to just run the
4
-
Redis Server.
5
-
6
-
There is no more real advantage of using SQLite for development, and instead it places a (relatively small) burden on
7
-
the developer to abstract inconsistencies away.
8
-
9
-
Which is why I decided for Lumina to stop supporting SQLite as a whole.