Gabor Körber
6 lines
421 B
Markdown
6 lines
421 B
Markdown
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
|
|
|