shiinee / eyefiserver Goto Github PK

I want to chown all transferred files once the transfer has completed. The eyefiserver is running as www-data (33) and I want to change the ownership to, say, 1000:1000. How would I do that?

My first approach was using the complete_execute config option:

complete_execute=/bin/chown 1000.1000

But this results in a python error with the subprocess:

OSError: [Errno 2] No such file or directory

I did some minor research, it seems that python is unable to call the system binary. But the reason remains a mystery to me.

PS: I'm trying to setup the eyefiserver within a docker container. I am using this base image. If I ever find a satisfactory way on how to do this I'll gladly provide a PR with the docker file and a detailed description. I'm having the image transfer working just fine, but changing the ownership after transfer would be very nice to have.

Like we have done with user-session-level systemd user units, we need a system-wide daemon unit that will start the eyefi daemon, and instructions on how to enable it. Upon enabling it, this unit should run with an already-preconfigured UNIX user that is created at RPM / DEB package install, should download photos to a predefined directory writable for the user and its group as well as g+s (so that people can be added to the group and they can take pictures out of said folder) and it should use the system-wide configuration file, which should come preconfigured to run directly, with only one change needed by the operator -- the upload key (which can in a suitable future be configured with a single command-line invocation of the utility to configure parameters).

Right now the preferences dialog shows italicized text telling the user to obtain the upload key, but that is of no help. Ideally, in both that dialog box and in the documentation of the project (man pages, README) there would be a hyperlink that takes the user to some page with step-by-step instructions for both Windows and Mac OS X to obtain the key.

Readme should be nicer, should explain that there is a makefile, should explain that there is a make RPM target, and should be markdown. This may require a few file renames.

It would be good if there was a configurator that would allow the user to configure the program as a system-level daemon (or even as a user-session-level daemon) with at least the same feature set as the current GUI program.

The GUI program and the command line configurator can share subroutines by using Python site-packages modules.

The GUI items require GTK+ and Python gobject introspection. This is probably a bad idea for someone who wants to run the program in a headless server. Create a separate RPM package (using the same spec file) to split those dependencies up.