Distributed system information query tool.
Find a file
2022-03-11 01:29:47 +00:00
docs Start setting things up for the HTTP subsystem, but we've got a ways to go 2022-02-10 21:42:53 +00:00
lantern-build-engine@094e175740 Add basic lantern build script to help with setting up for development 2022-02-26 00:19:22 +00:00
src client: add navigation item for dashboard 2022-03-11 01:29:47 +00:00
.gitignore Add initial client-side system 2022-02-22 03:01:39 +00:00
.gitmodules Add basic lantern build script to help with setting up for development 2022-02-26 00:19:22 +00:00
build.sh build.sh/launch: don't immediately exit on error 2022-03-10 02:49:04 +00:00
LICENSE Initial commit 2022-01-05 20:04:13 +00:00
package-lock.json Update dependencies 2022-03-10 02:49:15 +00:00
package.json client: bugfix new code 2022-03-10 23:58:12 +00:00
README.md Add initial client-side system 2022-02-22 03:01:39 +00:00

systemquery

Distributed system information query tool.

FAQ

Q: I see a scary native binary build system in the development dependencies!

A: You're probably referring to esbuild. If you install systemquery from npm, the build steps for the client-side javascript will already have been completed, thereby negating the need to install a native binary.

The advantage of using a build system for the client-side browser resources is significantly improved performance. With this approach, we get the benefit of a build system without needing to install a native binary on target machines which might be incompatible with the host machine's CPU architecture.

  • jpake - in case our STARTTLS-based idea doesn't work it didn't work :-/
  • sql.js - pure JS version of SQLite3 compiled with emscripten
    • This avoids the compiling-on-install problem may encounter with the regular better-sqlite3 package.