elabctl update said "Found latest release: 4.3.9" and pulled the images
in the logs I find "d41elabimg: info: eLabFTW version: 4.3.8"
any idea?
proper one is building: https://github.com/elabftw/elabimg/actions/runs/2759872771
FYI: it's this line that needs to be changed for a new version: https://github.com/elabftw/elabimg/blob/master/Dockerfile#L114
make sure to share some with the hardware!
@MarcelBolten I think this would be nice to implement once the link to experiment stuff is merged: https://github.com/elabftw/elabftw/issues/539#issuecomment-833675094
the release was a draft on github/elabimg
so curl -s https://api.github.com/repos/elabftw/elabimg/releases/latest | jq -r ".tag_name" would return incorrect release
I edited the /etc/elabftw.yml so that it's pulling 4.3.9, and it seems to have worked
probably some room for improvement in the workflow... anyway, new one is building: https://github.com/elabftw/elabimg/runs/7662749205?check_suite_focus=true
you can see the bug here: https://github.com/elabftw/elabimg/blob/master/.github/workflows/push_latest_image.yaml#L15
@NicolasCARPi root@elabftw-dev:~# curl -s https://api.github.com/repos/elabftw/elabimg/releases/latest | jq -r ".tag_name"
4.3.8
4.3.8
btw apiv2 is really taking shape, it'll be great once it's done, it allows deleting a lot of old ugly working code and replace it with fancy buggy code ^^
also, now you can directly access /api/v2/experiments/42 and get the json back in the browser
once I get things sorted out a bit better I'll post on the github discussion the current design
I think the releases of elabimg got marked as draft because I removed the tag corresponding
(and added it later)
as long as there are less lines of code at the end of the day I consider this a win
using the public api for internal stuff will be a game changer!
it's also a PITA, basically a superposition of both states
we need to show them the light!
BTW: current state of the APIV2 branch vs hypernext: 243 files changed, 4264 insertions(+), 6300 deletions(-)
I have a bit of a Problem using Borgbackup: everything appears to be configured correctly, no error in the terminal or anything. Borg list also shows me that I do have a backup. It is just that elabctl backup only creates the SQLdump but not the uploaded files zip archive anymore :(. Or does the backup process word fundamentally different now?