Can just add the raw log messages to a db table. Then it could be exposed on a page or API endpoint so you could see it without having to SSH in.
Any security implications here?
Can just add the raw log messages to a db table. Then it could be exposed on a page or API endpoint so you could see it without having to SSH in.
Any security implications here?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I think this can be done in the
framestable as long as the raw frame can be added to therawfield.Currently logging everything to
aprs_api.log. Adding to db would depend on what the error is.Can just add the raw log messages to a db table. Then it could be exposed on a page or API endpoint so you could see it without having to SSH in.
Any security implications here?