Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging #82

Open
SubSide opened this issue Oct 8, 2022 · 4 comments
Open

Logging #82

SubSide opened this issue Oct 8, 2022 · 4 comments
Assignees
Milestone

Comments

@SubSide
Copy link
Member

SubSide commented Oct 8, 2022

As an admin I want to be able to see who did what to the system.

Non exhaustive list:

  • Creations, edits, and removals of signups. and by who.
  • Creations, edits, and removals of mensas, and by who.
  • Changes to system settings.
  • Changes to faqs.

Add onto this when new log things are possible.
Find a nice way to link logs to certain mensas and faqs (maybe an uuid generated for every faq and mensa or something?)

@SubSide SubSide added this to the MVP milestone Oct 8, 2022
@Kipjr Kipjr self-assigned this Oct 9, 2022
@Kipjr
Copy link
Member

Kipjr commented Oct 14, 2022

we might need https://github.com/topclaudy/compoships for Logs & Categories for option 2 #97

@Kipjr
Copy link
Member

Kipjr commented Oct 16, 2022

see #96 and #97 for possible solutions. I would prefer Option 1.

@Kipjr
Copy link
Member

Kipjr commented Oct 16, 2022

idea for table-structure:

id = uuid
user_id = $user->id if user otherwise SYSTEM
content = json containing whatever data we want to store

@Kipjr
Copy link
Member

Kipjr commented Oct 31, 2022

It seems my current option does the above requirements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants