Rclone acts very much like scp or rsync, so there isn’t a need for a database. We will need some additional parameters in the fw_env: the remote to use and the root path in the remote.
This might be one parameter such as:
which will be split by the code to use the “gdrive” remote, copying the launch to garden/2017/launch_"
Moving files to the remote using rclone is: rclone copy :
Getting them is: rclone copy :
The only potential problem here is that this will require subprocess calls and not intrinsic python calls.
On Sunday, April 1, 2018 at 3:19:11 PM UTC-7, Anubhav Jain wrote:
files_in and files_out is meant to be pretty simple and without a lot of bells and whistles. If it can be made more powerful without interfering at all with the current operation or making it super complex (e.g., no adding to the database here), then sure.
The FilePad is supposed to be more where the heavyweight, database-based file operations go.
What exactly did you have in mind?
On Monday, March 19, 2018 at 11:17:09 AM UTC-7, [email protected] wrote:
It would be really nice to integrate a tool like rclone into Fireworks so that file location can be more agnostic. This post is meant to start a discussion on implementation.
I’m not fully sure where this should be accomplished. There is the files_in, files_out feature as well as Filepad. Should we compliment this file storage with some sort of mongodb based index?