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
Sorry, the error is
manifest unknown
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
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?
@paullysa yes. You can PATCH
api/v2/experiments/257/steps/53 with in the request body an action: finish to toggle the finished step of a step. You can PATCH /items/432 with an action "Lock" to toggle lock and you can PATCH with an action:bloxberg to send it to blockchain. Basically the WEB UI is now using the api directly, so for 99% of actions that can be done through the web interface, they can also be done through the REST API because it's using the same endpoint ;)
Hello everyone, I have installed on local server elabftw, also I have to point certificate path with change line /ssl in YAML. The tutorial notice to elabctl restart, I must to stop container before or just restart while container running is enough to take account of modifications ? thanks a lot , i'm not expert in docker ;)
Hi everyone! I try to set up eLab for a research lab with different sites. We would like to share some database entries between sites (which means we want to link the same database entry in experiements on each site). At the moment we decided to design a site as a 'team'.
Now it's possible to see details of attached database entries - but it's neither possible to see the database entries from the other team in the database section nor to link them to a an experiment.
Is this a general design decission or did I do something wrong in the setup?
Now it's possible to see details of attached database entries - but it's neither possible to see the database entries from the other team in the database section nor to link them to a an experiment.
Is this a general design decission or did I do something wrong in the setup?
Is it possible to get more detail on setting up SMTP in the install guide? I'm running into errors when I try to send the test email even though I've got SMTP2GO set up. I'm fairly certain that the issue is the
Sender Address: field, but that's not covered in the install guide
(I'm sure this is probably assumed knowledge for most sysadmins but it's new to me)
There could also be issues related to the University firewall (in fact there are almost certainly issues related to that), but I'm not certain without a bit more detail on the expected config
@besselfunct your first step must be to look at the error in the log instead of guessing what could be the issue. See https://doc.elabftw.net/debug.html
Hello all! I have a problem updating elab to the latest version.
We are running elabftw in Docker on ubuntu. I did the Update via elabctl update, and it was completet successfully. After that, we needed to add the SITE_URL variable to the docker yml, so that the WEB UI is working again.
The WEB UI shows, that we have to run the "bin/console db:update" command to finish the update, but when run this command on the ubuntu cli, we get the following permission denied error.
"1227 Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABlES_ADMIN privilege(s) for this operation.
Does anyone know whats going on here? Everything is set up with default config.
We are running elabftw in Docker on ubuntu. I did the Update via elabctl update, and it was completet successfully. After that, we needed to add the SITE_URL variable to the docker yml, so that the WEB UI is working again.
The WEB UI shows, that we have to run the "bin/console db:update" command to finish the update, but when run this command on the ubuntu cli, we get the following permission denied error.
"1227 Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABlES_ADMIN privilege(s) for this operation.
Does anyone know whats going on here? Everything is set up with default config.
I upgraded elabftw from ver 4.2.4 to 4.3.10 in Ubuntu 18.04. In this new version (not in old version), attached files with Japanese filename is downloaded as that a file with "". For example, the filename is changed to "protocol_.docx" (_ should be in Japanese). What's wrong? How can I solve the problem?
@sysopls I think you run into this: https://github.com/elabftw/elabftw/discussions/3592#discussioncomment-3268365 try the solution and report back
2 replies
@sakuraabcdef Wait, I figured out something. I was not using the filename fallback. Because only the fallback must be ASCII!!! So now the correct filename will be downloaded, and only the fallback filename is in ascii!