.

2026-05-06 19:32:29 +02:00
parent b029b4b975
commit b82607a31c
1 changed files with 4 additions and 0 deletions
@@ -1,2 +1,6 @@
 Atm. it is not clear to me if rear_auth will really be it's own package, as it needs to interact a lot with rear, or if I split up rear into modules instead.
 Another idea would be to:
 - create rear as a basic set of tools for a homepage, like commonalities you would require
 - transform rear_auth into rear_admin, utilizing the repository patterns and template engines from rear for providing an admin interface