You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once that PR gets merged... can look into creating routes and implementing CRUD for From/To Service Checks
Would be nice to have a discussion on what to the database schema could start looking like. As @AlbinoDrought started his initial work on the notification base, it would be invaluable to have his input 👍
Here's what the initial database schema could look like imo:
tableName: services
- id [PK]
- user_id [FK][users]
- name
- type [to, from]
tableName: checks or actions
- id [PK]
- service_id [FK][services]
- process [request, ping, etc]
- source [ip, domain, etc]
Not too sure how the actions for each service should be stored...
The text was updated successfully, but these errors were encountered:
Once that PR gets merged... can look into creating routes and implementing CRUD for From/To Service Checks
Would be nice to have a discussion on what to the database schema could start looking like. As @AlbinoDrought started his initial work on the notification base, it would be invaluable to have his input 👍
Here's what the initial database schema could look like imo:
tableName: services
tableName: checks or actions
Not too sure how the actions for each service should be stored...
The text was updated successfully, but these errors were encountered: