Storage hook query

[bitb526]

Hi,

I hope this is the correct section to ask this question.

I'm a long time user of Radicale since the days of 2.0 and I believe it is the best simple CalDav server out there.

I've recently upgraded to V3 (3.1.8 is the latest available on Debian).

I am having an issue using the storage hook and I was hoping someone might be able to tell me if what I am attempting to do is correct.

The Objective: I am trying to intercept put requests for events from the client to process and make a change to the event ICS on the fly when an update/create is made.

The Method: I am using a hook python script setting the path to the script in the config file. My understanding (which may be wrong) is that when the script is called from Radicale, the ics data will be piped in to the hook process on stdin and the modified version can be written to stdout for Radicale to use as normal.

The problem I have is that although the script is called and I can get stderr messages logged in debug from the hook script, it appears that stdin is not being piped any data at all from Radicale.

Have I misunderstood how this is meant to happen or am I doing something wrong somewhere?

Can anyone please confirm that I should be seeing the ICS data on stdin in the hook file process?

Thanks for your time.

[pbiering]

3.1.8 is from Jul 14, 2022 and no longer suported, but you can overload the packaged files with current ones, all should stay compatible.

Code of storage hook is here

Radicale/radicale/storage/multifilesystem/lock.py

Line 51 in 348b123

class StoragePartLock(StorageBase):

• stdin=subprocess.DEVNULL -> nothing is piped into the script

-> your script has to read the content from path and write it back to the same, see also

Radicale/config

Line 232 in 348b123

# Command that is run after changes to storage, default is emtpy

Your assumed feature would be a pipe one, so far not implemented, question would be also where to add incl. lock to avoid any race condition.

[bitb526]

Thanks for taking the time to reply.

Great info, just what I needed, thank you. That all makes sense and I shall modify my code accordingly.

Thanks again.