File attachments via API

[mariomare22]

❓ Question
Is the a possibility beides sending a picture to telegram to send a log file?

Thanks

[caronc]

Sure you can:

# Below I've added my configuration to ~/.apprise and kept my telegram
# entry tagged as telegram
 apprise -t "my log" -b "see attached" --attach /var/log/messages -g telegram

# But you could just spell out the whole URL too this way:
 apprise -t "my log" -b "see attached" --attach /var/log/messages tgram://apprise/url/details

[mariomare22]

Thaaaanks!
how can I do it with the api? if possible?

[caronc]

No unfortunately.

I'm not sure the best way to go about implement something like that. I'd have to build it in such a way where you post the attachment with the notification itself. To add attachment support adds an element of Denial of Service since you can technically post a lot and fill the file-system. I'd have to have something clean up uploads that had been already notified.

Your request is definitely do-able, but I'd have to think of a effective way of doing it.

I'll move this ticket over to the Apprise-API project.

[mariomare22]

I think I found a workaround:
docker exec apprise apprise -t "my log" -b "see attached" --attach /config/test.txt -g tg_grp --config=http://localhost:8080/get/zfstg

This works but implies that I have previously copied the log file into the container or I have mounted a volume on the host.
Thanks!

[caronc]

I'm glad you found a workaround. If you want to take that approach, you could add --mount and mount stuff to be available inside your container for messaging purposes that exist outside (see here).

$ docker run -d \
  --name=apprise \
  --mount source=/path/on/local/filesystem,destination=/path/on/docker/filesysteml,readonly \
 ...

That way you don't need to use the COPY directive. You can just access whatever is current that you popped into your share.

[mariomare22]

Yup this is what I am doing! closed for me, Thank you

[schklom]

@caronc

To add attachment support adds an element of Denial of Service since you can technically post a lot and fill the file-system

Not necessarily. Write a warning in capital letters and let the feature be disabled by default if you want, but I personally do not mind this attack vector because I restrict the API for my personal use (basic auth on the reverse-proxy).

I have a feeling I am far from the only person who only uses Apprise only for themselves.

If the day comes that my username and password for basic auth are leaked, it means they will have access to all my other passwords, and a Denial of Service will be the least of my worries.

[caronc]

Will reopen for reconsideration

[caronc]

Attachment support is complete and merged as part of the latest Apprise API and is only compatible with the latest version of Apprise (v1.4.0) just released today as well.