commit cbcc1d2ef0425a700b41a49d89f2e2170ae23c27
parent 2e802ea23a088290830a57442f7463a7ec9b66c7
Author: Brennen T. Mazur <brennen@madis.cool>
Date: Mon, 9 Jan 2023 01:15:00 -0700
remove unnecesary files, update READMEs for clarity
Diffstat:
4 files changed, 13 insertions(+), 18 deletions(-)
diff --git a/README b/README
@@ -8,9 +8,6 @@ Project has potential to be renamed to scms (simple content management system) b
An option would be to create the base structure for the cms (as human resource management [ex. time tracking]) and allow patches to include additional functionality like equipment tracking etc. Allows no-nonsence approach to anti-bloat management software.
-Work is currently ongoing on the wireframe for the landing dashboard and signin page.
-
-webapp setings are located in config.py
db file will likely be /scms.db or whatever the appname resolves to
templates holds each "component" either a standalone file, or a directory for a index.html(full page route) and widget.html(dashboard interactable view)
diff --git a/README.planfor b/README.planfor
@@ -1,8 +1,18 @@
#Plan for getting appropriate modules
-on successfull auth -> base.html calls getModules(),
- getModules() retrieves permissions[] value from db.users
- returns string of {% block $module %}{% endblock %} for each value in permission
+on successfull auth -> base.html utilizes successfulAuth() -> ?validUSR?[user-name(str), accessable modules[array], server-connection(bool)]
+ accessable modules and server-connection are used for navbar creation and to check if local-storage is necessary for temp operations
+ user-name used for welcome "prompt"
+each route checkAuth() -> directs to login if false, else
+ calls routeblock
+
+Routeblocks getRelevantData(not necessarily one fn, likely individual) -> relevantData[clocked-in,project,purdium,lunch]
+ used to populate ?MACRO? for displayed widget/page
+ should checkAuth() # We should be checking constantly for auth to verify and doubleverify before any exchange of data or operations
+#####
+I've overcomplicated this, the responses can be parsed as the raw JSON data returned from the db... Everything will request relatively small amounts of data until the reports which will likely need to make multiple calls? then return a txt/pdftex file
+
+#####
This implies you have db.users.$user.permission[val1,val2,...]
/admin.html should have 'preset' permissions per role and allow toggling individual level
diff --git a/config.py b/config.py
diff --git a/setup.py b/setup.py
@@ -1,12 +0,0 @@
-from setuptools import setup
-
-setup(
- name='stc',
- packages=['stc'],
- include_package_data=True,
- install_requires=[
- 'flask',
- 'flask_login',
- 'flask_bcrypt',
- ],
-)
