amyipdev / ssvp Goto Github PK

have event updates be available via activitypub in addition to rss, email, etc

all looks wrong, need to document so people understand that SI is not approproiate

Any module which uses sockets does not properly support pinging over IPv6. this needs to be investigated

A current concern is that because of the amount of I/O overhead, there's a lot of downtime for subprocesses. Perhaps the amount of pool workers should be 4*nproc, or even more.

While the all-time uptime is updated correctly (or at least it appears to be - might have issues of its own), the monthly and yearly uptimes are not being done correctly. This may be because of the usage of intervals.

daily stats are not being overriden correctly. this needs to be fixed to show history properly

have an option to automatically create an event on toggle - when admin alerts are created this should be trivial

There should be configuration options, like port number

there should be a way to indicate the SSVP version in the web interface

also, does this mean we should switch to + at the end of WIP releases to indicate git?

Old branches should be cleared up and deleted to not pollute the repo

this should be put in the documentation as a specification, and also autodetected when running certain scripts

of course for this we need to determine the minimum viable versions of different software

perhaps this could be overall done with a check_dependencies.sh or python script? this could check for other software dependencies as well as correct versions. python might be easier for handling semvers

services keep going which is clearly a problem

need to figure out uninstall hooks

the popovers should use html so we can get colored text, and a table for explaining events

We should support more package managers (main one I can think of is pacman)

• Config generator
• Database initializer
• Cached stats initializer
• make install
• Wrapper file (runs everything, calls make install)

The following are all of the newly proposed features:

• Native SSL support
• SSL toggleswitch: done
• Actual SSL implementation: done
• Automatic port selection: done
• ACME: done
• Internationalization
• Cookie setting support (TS-handled via navbar dropdown): not done
• Cookies read by server: not done
• HTML i18n support: not done
• TS i18n support: not done
• Spanish translation: not done
• Chinese translation: not done
• Minification
• CSS: not done
• JS: not done
• HTML: not done
• Services
• Card: done
• Backend: done
• PostgreSQL support
• Events support
• SQLite3 support
• InfluxDB support
• MongoDB support
• Basic module set:
• ping: done
• http: done
• tcp: done
• ssvplwc: done
  • server-side: done
  • client-side: done
• Autorefresh every 60 seconds
• Distribution
  • .deb: not done
  • .rpm: done
  • PKGBUILD: not done
  • nix: done
• Install script
• make install
• AGPLv3-ification
  • SPDX headers: done
  • LICENSE file: done
• README
• Offer WSGI server options
  • Apache2: https://flask.palletsprojects.com/en/2.3.x/deploying/mod_wsgi/: not done mod_wsgi does not behave correctly and appears to have generally fallen out of active support
  • Gunicorn: https://flask.palletsprojects.com/en/2.3.x/deploying/gunicorn/: done
  • uWSGI: https://flask.palletsprojects.com/en/2.3.x/deploying/uwsgi/: not done while possible to adapt, uwsgi is its own mess, and gunicorn works just fine - no need to use it
  • Werkezurg/internal: done
• API Latency Module
• Bar Tooltips
• Internal Mode
• Login System (also allow internal mode to be displayed without login)
• Modules (RAM, CPU, disk, network) (each one can be enabled/disabled by adding them into a json list, list is dynamically fetched, modules in order)
• All available modes (disabled, login - front page shows internal, login required, nologin - front page shows internal, dual - /internal requires login and shows internal, / is standard and doesn't require login, jinja-added nav option for /internal called "Advanced")
• Alerts
• Internal: canceled feature in favor of email system
• External: RSS, Atom done, activitypub, email not done

There are plenty more already planned ideas to add to this list, and they will be added eventually. Newly proposed ideas will also be added.

This list is dynamic; it will update as new ideas are presented, and as they are completed.

fedora/EL want signed RPMs but its not mandatory

its mandatory for SUSE

All bash files should have shebangs. This doesn't need to be done for Python since we don't support running Python directly (fileperms & 111 = 000)

default to searching relative to the local directory when applicable

A formal API specification should be made in the docs.

we need testing suites for a lot of this - difficult, but still possible

needs to support a large variety of platforms (debian, ubuntu, fedora, centos, alma, rocky, nixos, etc)

chrome mobile is the only browser with zero functionality, likely a silent JS error

socials should display properly for their embeds

Trying to build RPMs on Enterprise Linux has the following issues:

• nodejs-npm -> npm, which affects:
  • building RPMs (must patch the specfile)
  • the dependency autoinstaller (from install.sh)

The bars should have small indicators for how many days are being shown

<tbody> is not required, when there is no other table section, but it is recommended. Firefox automatically inserts it. We should consider doing the same as well.

this is important for terminal accessibility

RST might not need to be, but global MD probably should

add quick reload functionality for gunicorn

this could be made easier with systemd

get in nixpkgs - requires several changes, such as adding meta fields

SQLite3, PostgreSQL, and MySQL may be able to be abstracted (share most of the same code) via DB-API; this should be looked into

See TODO in srv/dbhandle.py

pylint, cargo fmt, eslint, etc

the email subscribe button should only be conditionally enabled based on config["email"] being defined

this also goes for ActivityPub dependencies on keypairs

In case someone wants to remove SSVP, there should be a clean uninstaller

databases might want to consider switching to bigints/bigserial for eventID in ssvp_events

lots of things fail without ghost entries in some categories. make sure people run interval.py first, also clarify any other entries that need to be pre-made first (like cached stats?)

gen_config sets up servers but not services. probably should dedup the code since it's the exact same for both of them

A checklist should be made that is run through before tagging a release.