I have an Apache web server on a Raspberry Pi 3 and a CIFS mount on the
Pi 3 which is Raspbian Stretch Linux based. The windows client has the
same CIFS mount. I want an Apache hosted web site from the Pi
to launch windows explorer on the Windows client machine so that the
client can add a file to the CIFS share and the Pi getting the name of
the new file can copy it off of the CIFS share.
Put another way, Windows client needs to upload a file to a Windows
network drive that the Linux based
Pi sees too. Client should indicate which file via Windows Explorer.
The name of the new file on the CIFS share needs to get to the Apache
web server and a bash shell script will copy the new file to somewhere
on the Pi, say to a ram drive. So if the client needs to copy from
somewhere_on_windows:\file.tps to CIFS_share:\file.tps, I need to know
about file.tps server side as
soon as it arrives on the CIFS share. Preferably, I don't copy the file
again if I have a copy that
is no different from the one requested Pi side.
Having a CIFS mount is the current approach, but what's stopping me from
having an (s)ftp server on the
Pi and having the Windows client do an ftp or sftp upload?
Note that I only need a file name on the CIFS share server side. I
don't need to write anything on the client, that is the client's
responsibility. All I ever need to do Linux side is read files off of
the CIFS share under the direction of the client. What is the best and
proper way to do this in a LASP
stack? L is for Linux, A is for Apache, S is for sqlite3, and P is for
PHP.
_______________________________________________
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
