Explorar o código

add notes on rclone

Your Name hai 8 meses
pai
achega
c4cd925b16
Modificáronse 5 ficheiros con 25 adicións e 0 borrados
  1. 22 0
      README.md
  2. BIN=BIN
      images/passphrase-prompt.png
  3. BIN=BIN
      images/premission-denied.png
  4. BIN=BIN
      images/rclone-sync.png
  5. 3 0
      rclone.conf

+ 22 - 0
README.md

@@ -73,6 +73,8 @@ Encrypting private keys to prevent a number of security flaws will expose us to
 
 Using the shortcut we just created, we will provide `Pageant` a way to find our key.
 
+![shell-startup-explorer-window](images/pageant-shortcut.png)
+
 The Windows properties dialog window has a tab, `Shortcut` with a `taget` property that you will set to a value like this:
 ```
 "C:\Program Files\PuTTY\pageant.exe" --encrypted C:\Users\valued-customer\Desktop\windows-rclone-key-for-kyleguy.ppk
@@ -110,6 +112,26 @@ cp 'C:\Users\valued-customer\AppData\Roaming\rclone\rclone.conf' 'C:\Users\value
 ![create-rclone-configure-file](images/rclone-config-create.png)
 ---
 
+**Hugo Rclone Deploy**
+
+When we are happy with the results of our work on the local development computer, we can deploy the site to `kyleguy.rome7.com` using the following command snippet:
+
+```
+cd Desktop\kyleguy
+rclone sync --config rclone.conf web\public\ kyleguy:/mnt/external/projects/kyleguy/web/public/
+```
+![rclone-sync](images/rclone-sync.png)
+
+The first time we do this `Pageant` will prompt us to provide the passphrase for our encrypted private key:
+![pageant-passphrase-prompt](images/passphrase-promt.png)
+---
+
+**Just in-case you get a permission denied**
+
+![troubleshoot-permission-denied](images/permission-denied.png)
+
+This is just because your user is not allowed to write files to the target location.  You'll log into pebbleguy.com and use `ls -lathr` on the directory you are trying to copy into and look at the permissions.  Right now it is out-of-scope to explain users and permissions.  I expect that with so many users "helping" eachother out that we should all be familiar with the side effects of what happens when we accidentally forget about permissions.  In general all the admin users have been added to a group, `www-data`.  By default files created by a user are owned by that user.  This is the root cause of these accidents but is a sane method for file creation.  We should learn to be cognizant of the environment we are in and not expect that anyone but ourselves are able to know what our intentions were.
+
 
 ## a place called home, or maybe webroot
 Base directory.  Home.  Root.  C Drive.  What other names are there? Maybe `A:` or `/`.  The place that is the container for the stuff.  Or the directory that holds all the files.  Folders if you like that better.  The `webroot` is a name that does not mean anything except for when you care about it.  If it were your job to organize a party you'd probably pick a place and tell everyone to meet there.  For this tiny amount of time that location is special.  It is ground zero for where the party will happen.  People who aren't at the specified location aren't at the party.  Your party isn't the only party.  In fact it might not even be the only party at the location that you picked.  The point is that you picked a location made it special because you said it was.  This is the same for a webroot.  You are just picking some arbitrary location on a disk and you are going to tell everyone if they want to party at your website they need to go there.  When you follow the instructions for the site setup you will need to tell `NginX` about this location.  I am going to pick the location and we are going to put some files there to serve up at the party.  How long can I draw out this metaphore?  Forever.

BIN=BIN
images/passphrase-prompt.png


BIN=BIN
images/premission-denied.png


BIN=BIN
images/rclone-sync.png


+ 3 - 0
rclone.conf

@@ -3,4 +3,7 @@ type = sftp
 host = pebbleguy.com
 user = jb6113
 key_use_agent = true
+shell_type = unix
+md5sum_command = md5sum
+sha1sum_command = sha1sum