You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like the option to not cache images locally, and instead only upload them. This means that the program will not hang and wait for input when the image directory does not exist. I simply want to scp an image file without leaving a trace locally. Possible or planned?
The text was updated successfully, but these errors were encountered:
recent maim update has it spitting the image straight to STDOUT.. so theoretically its possible...
something like this could be used to make the SCP uploader work. When dealing with the HTTP uploaders, it would be much easier sicne im sure curl has a way to grab the body from STDIN.
In the meantime, you could just tell it to put cache the images in /tmp/ so that they get cleared every reboot.
I personally think this is unlikely to get in.. everything is so much easier when its a simple file rather than if its a stream... even if STDIN is technically just a file.
In theory it would be nice if each operation had a keyword (save, upload, delete, eg...), which can be chained. But this would need quite some restructuring.
Using /tmp/ is what I have been doing, and the reason for this issue is because on my machine, that is a ramdisk that has a lifetime of several months before I reboot. Remembering to clear that so I don't swap to disk is a real pain. Thanks anyway.
I would like the option to not cache images locally, and instead only upload them. This means that the program will not hang and wait for input when the image directory does not exist. I simply want to scp an image file without leaving a trace locally. Possible or planned?
The text was updated successfully, but these errors were encountered: