Velcom 2.0 written in Rust
Find a file
2023-10-24 14:24:58 +02:00
.sqlx Fetch and process commits 2023-10-23 22:16:53 +02:00
.vscode Switch to ES2022 2023-10-22 01:50:19 +02:00
meta Remove stddev and direction columns 2023-10-22 01:50:19 +02:00
migrations Improve graph query performance 2023-10-23 22:48:35 +02:00
scripts Create normal and day-equidistant commit date arrays 2023-10-24 14:24:58 +02:00
src Fix error if no config file exists 2023-10-24 00:27:03 +02:00
static Style commit-like entities 2023-08-18 03:11:13 +02:00
templates Create metric selector via JS 2023-10-22 01:50:19 +02:00
.env Fix project not compiling without dev.db 2023-08-05 16:20:32 +02:00
.gitignore Create project 2023-08-03 14:32:37 +02:00
askama.toml Use askama to render test template 2023-08-03 19:14:58 +02:00
build.rs Silence warnings for unused static files 2023-10-24 10:31:01 +02:00
Cargo.lock Update dependencies 2023-10-22 01:50:19 +02:00
Cargo.toml Update dependencies 2023-10-22 01:50:19 +02:00
DESIGN.md Stream repo and bench repo worktree tars 2023-08-11 14:42:39 +02:00
README.md Set up and document uPlot 2023-08-14 17:45:33 +02:00
tsconfig.json Switch to ES2022 2023-10-22 01:50:19 +02:00

tablejohn

Run benchmarks against commits in a git repo and present their results.

Building from source

The following tools are required:

Once you have installed these tools, run the following command to install or update tablejohn to ~/.cargo/bin/tablejohn:

cargo install --force --git https://github.com/Garmelon/tablejohn

Alternatively, clone the repo and run cargo build --release. The compiled binary will be located at target/release/tablejohn.

The binary produced by either of these steps contains everything needed to run tablejohn. Not additional files are required.

Developing

I recommend using VSCode and rust-analyzer in combination with the tools mentioned in the previous section. However, some parts of the code base require additional tools and setup.

Changing SQL queries with sqlx

If you want to change any of the SQL queries, you will need to install sqlx, the CLI of the sqlx library. The sqlx library can connect to a dev database at compile-time to verify SQL queries defined via the query* macro family. This is useful during development as it gives immediate feedback on mistakes in your queries. However, it requires a bit of setup. During normal compilation with cargo build, the cached query analyses in .sqlite/ are used instead of the dev database. This way, the dev database and sqlx tool is not required when you're just building the project.

First, run ./meta/setup. This creates or updates the dev database at target/dev.db. You will need to rerun this command whenever you change or add a migration.

Then, if you don't use VSCode, configure your rust-analyzer to run with the with the environment variable SQLX_OFFLINE=false using the rust-analyzer.server.extraEnv option. This signals to sqlx that it should use the dev database instead of .sqlx/, but only in your IDE.

Important: Before committing any changed SQL query, you must run ./meta/update_sqlx_queries. This will recreate your dev database (just like ./meta/setup) and then update the files in .sqlx/.

uPlot

For displaying graphs, the uPlot library is used. Because this is the only dependency on the JS side, I decided not to use a package manager and instead just add the library files directly.

To update the uPlot files, run ./meta/update_uplot. This will download the required files from uPlot's master. The uPlot.d.ts file's export statement is patched to resemble the one in uPlot.js. This way I don't have to enable esModuleInterop in my tsconfig.json.