Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
public:gsoc:rcloneweb [2019/02/07 21:23]
cfsmp3
public:gsoc:rcloneweb [2019/02/16 21:09] (current)
nick Notes from Nick Craig-Wood
Line 22: Line 22:
  
 If you have experience with frameworks then you have probably seen it. If not, do a bit of research. It's easy to implement, but you have to implement it. This is an essential requirement - users often want to use a separate web server to handle security, certificates and so on, and they don't want to open a different port of each web interface. If you have experience with frameworks then you have probably seen it. If not, do a bit of research. It's easy to implement, but you have to implement it. This is an essential requirement - users often want to use a separate web server to handle security, certificates and so on, and they don't want to open a different port of each web interface.
 +
 +====== Notes from Nick Craig-Wood ======
 +
 +I have quite a few ideas on rclone web GUIs.  I've been gradually fleshing out the API https://​rclone.org/​rc/​ so that it can control rclone completely.
 +
 +Rclone can also just run the remote control, serve files and open your browser with
 +
 +    rclone rcd --rc-serve --rc-noauth --rc-files /​path/​to/​files
 +
 +So that should be enough to build a remote control interface entirely with web technologies. ​ The `--rc-server` means rclone can serve the remote files too.
 +
 +I made a very proof of concept react app (to show that the rc API was usable by react), but that is as far as I got!
 +
 +I stuck it on github here: https://​github.com/​ncw/​rcloneguiexperiment
 +
 +That is how I imagine development might go, but I could also imagine bundling a version of rclone with the web GUI packaged in, so you could just run `rclone gui` (or maybe even just double click) and get the web interface. ​
  
  • public/gsoc/rcloneweb.txt
  • Last modified: 2019/02/16 21:09
  • by nick