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
Would be amazing to have some information around what version the torii is running, for example we had some instances on Eternum where we weren't sure anymore of what version was running on a remote torii (or commit hash, as we were running some versions from different branches often as well).
It wasn't possible to get the specific version unless with slot command, or having to ask the maintainer of the instance.
My proposed solution is to store the version and commit hash of the torii binary as start. It would be stored inside a version table in the database to be able to run an SQL query and retrieve that version
The text was updated successfully, but these errors were encountered:
edisontim
changed the title
[torii] Had version and commit hash in the metadata table
[torii] Add version and commit hash in the metadata table
Jan 10, 2025
edisontim
changed the title
[torii] Add version and commit hash in the metadata table
[torii] Add version and commit hash in a version table
Jan 21, 2025
Would be amazing to have some information around what version the torii is running, for example we had some instances on Eternum where we weren't sure anymore of what version was running on a remote torii (or commit hash, as we were running some versions from different branches often as well).
It wasn't possible to get the specific version unless with
slot
command, or having to ask the maintainer of the instance.My proposed solution is to store the version and commit hash of the torii binary as start. It would be stored inside a
version
table in the database to be able to run an SQL query and retrieve that versionThe text was updated successfully, but these errors were encountered: