yep the testing flag has been removed I set the command to upgrade it manually by the cli
When a task is created, it's validated and added correctly to the list. However,…
yep the testing flag has been removed I set the command to upgrade it manually by the cli
for now it is just a talk, no decisions have been taken
Well, what is the command? (to test this)
I hope some decision is made because for SOHO worldwide, a front-end (always online) and a back-end mail server is very common setup still (for people that haven’t moved to full cloud solutions).
Something needs to be done so that rules work in any setup.
Even server (not sieve I think) own automatic forwarding doesn’t work.
(I know because I tried to trick the system - see the thread for details)
Anyway I don’t want to destroy this thread, please give me the command to get the test version of imapsync.
thank for your help but please you should read the description of the issue to understand what to test
When a task is created, it's validated and added correctly to the list. However,…
the command is :
api-cli run update-module --data '{"module_url":"ghcr.io/nethserver/imapsync:1.0.4-dev.3","instances":["imapsync1"],"force":true}'
Yes I understand what to test.
I will revert when I see the result.
OK, imapsync is now 1.0.4-dev.3 (also mail updated to 1.4.8)…
Edited a task with cr*p and pressed cancel.
It kept the previous details (the correct ones).
I changed more values, clicked cancel.
Again, it indeed canceled and didn’t keep the bad values.
So yes, works.
BTW, I wish the option to enable testing comes back (or maybe there is a central setting in settings). Admins are admins.
BTW, I wish the option to enable testing comes back (or maybe there is a central setting in settings). Admins are admins.
It exists
NS8 - Developer manual
redis-cli HSET cluster/repository/default testing 1
hello nick, do not forget it we need to release
But I did test it and it worked. My post is above, 6 days ago.
thank a lot nick…I missed it, sorry