diff options
Diffstat (limited to 'content/2020-09-09-digitalocean-sync.md')
| -rw-r--r-- | content/2020-09-09-digitalocean-sync.md | 112 |
1 files changed, 112 insertions, 0 deletions
diff --git a/content/2020-09-09-digitalocean-sync.md b/content/2020-09-09-digitalocean-sync.md new file mode 100644 index 0000000..e16b827 --- /dev/null +++ b/content/2020-09-09-digitalocean-sync.md | |||
| @@ -0,0 +1,112 @@ | |||
| 1 | --- | ||
| 2 | title: Using Digitalocean Spaces to sync between computers | ||
| 3 | url: digitalocean-spaces-to-sync-between-computers.html | ||
| 4 | date: 2020-09-09T12:00:00+02:00 | ||
| 5 | type: post | ||
| 6 | draft: false | ||
| 7 | --- | ||
| 8 | |||
| 9 | I've been using [Dropbox](https://www.dropbox.com/) for probably **10+ years** | ||
| 10 | now and I-ve became so used to it that it runs in the background that I don't | ||
| 11 | even imagine a world without it. But it's not without problems. | ||
| 12 | |||
| 13 | At first I had problems with `.venv` environments for Python and the only | ||
| 14 | solution for excluding synchronization for this folder was to manually exclude a | ||
| 15 | specific folder which is not really scalable. FYI, my whole project folder is | ||
| 16 | synced on [Dropbox](https://www.dropbox.com/). This of course introduced a lot | ||
| 17 | of syncing of files and folders that are not needed or even break things on | ||
| 18 | other machines. In the case of **Python**, I couldn't use that on my second | ||
| 19 | machine. I needed to delete `.venv` folder and pip it again which synced files | ||
| 20 | again to the main machine. This was very frustrating. **Nodejs** handles this | ||
| 21 | much nicer and I can just run the scripts without deleting `node_modules` again | ||
| 22 | and reinstalling. However, `node_modules` is a beast of its own. It creates so | ||
| 23 | many files that OS has a problem counting them when you check the folder | ||
| 24 | contents for size. | ||
| 25 | |||
| 26 | I wanted something similar to Dropbox. I could without the instant syncing but | ||
| 27 | it would need to be fast and had the option for me to exclude folders like | ||
| 28 | `node_modules, .venv, .git` and folders like that. | ||
| 29 | |||
| 30 | I went on a hunt for an alternative to [Dropbox](https://www.dropbox.com/) | ||
| 31 | and found: | ||
| 32 | |||
| 33 | - [Tresorit](https://tresorit.com/) | ||
| 34 | - [Sync.com](https://sync.com) | ||
| 35 | - [Box](https://www.box.com/) | ||
| 36 | |||
| 37 | You know, the usual list of suspects. I didn't include [Google | ||
| 38 | drive](https://drive.google.com) or [One drive](https://onedrive.live.com/) | ||
| 39 | since they are even more draconian than Dropbox. | ||
| 40 | |||
| 41 | > All this does not stem from me being paranoid but recently these companies | ||
| 42 | > have became more and more aggressive and they keep violating our privacy when | ||
| 43 | > they share our data with 3rd party services. It is getting out of control. | ||
| 44 | |||
| 45 | So, my main problem was still there. No way of excluding a specific folder from | ||
| 46 | syncing. And before we go into "*But you have git, isn't that enough?*", I must | ||
| 47 | say, that many of the files (PDFs, spreadsheets, etc) I have in a `git` repo | ||
| 48 | don't get pushed upstream to Git and I still want to have them synced across my | ||
| 49 | computers. | ||
| 50 | |||
| 51 | I initially wanted to use [rsync](https://linux.die.net/man/1/rsync) but I would | ||
| 52 | need to then have a remote VPS or transfer between my computers directly. I | ||
| 53 | wanted a solution where all my files could be accessible to me without my | ||
| 54 | machine. | ||
| 55 | |||
| 56 | > **WARNING: This solution will cost you money!** DigitalOcean Spaces are $5 per | ||
| 57 | month and there are some bandwidth limitations and if you go beyond that you get | ||
| 58 | billed additionally. | ||
| 59 | |||
| 60 | Then I remembered that I could use something like | ||
| 61 | [S3](https://en.wikipedia.org/wiki/Amazon_S3) since it has versioning and is | ||
| 62 | fully managed. I didn't want to go down the AWS rabbit hole with this so I | ||
| 63 | choose [DigitalOcean Spaces](https://www.digitalocean.com/products/spaces/). | ||
| 64 | |||
| 65 | Then I needed a command-line tool to sync between source and target. I found | ||
| 66 | this nice tool [s3cmd](https://s3tools.org/s3cmd) and it is in the Ubuntu | ||
| 67 | repositories. | ||
| 68 | |||
| 69 | ```bash | ||
| 70 | sudo apt install s3cmd | ||
| 71 | ``` | ||
| 72 | |||
| 73 | After installation will I create a new Space bucket on DigitalOcean. Remember | ||
| 74 | the zone you will choose because you will need it when you will configure | ||
| 75 | `s3cmd`. | ||
| 76 | |||
| 77 | Then I visited [Digitalocean Applications & | ||
| 78 | API](https://cloud.digitalocean.com/account/api/tokens) and generated **Spaces | ||
| 79 | access keys**. Save both key and secret somewhere safe because when you will | ||
| 80 | leave the page secret will not be available anymore to you and you will need to | ||
| 81 | re-generate it. | ||
| 82 | |||
| 83 | ```bash | ||
| 84 | # enter your key and secret and correct endpoint | ||
| 85 | # my endpoint is ams3.digitaloceanspaces.com because | ||
| 86 | # I created my bucket in Amsterdam regiin | ||
| 87 | s3cmd --configure | ||
| 88 | ``` | ||
| 89 | |||
| 90 | After that I played around with options for `s3cmd` and got to the following | ||
| 91 | command. | ||
| 92 | |||
| 93 | ```bash | ||
| 94 | # I executed this command from my projects folder | ||
| 95 | cd projects | ||
| 96 | s3cmd sync --delete-removed --exclude 'node_modules/*' --exclude '.git/*' --exclude '.venv/*' ./ s3://my-bucket-name/projects/ | ||
| 97 | ``` | ||
| 98 | |||
| 99 | When syncing int he other direction you will need to change the order of the | ||
| 100 | `SOURCE` and `TARGET` to `s3://my-bucket-name/projects/` and `./`. | ||
| 101 | |||
| 102 | > Be sure that all the paths have trailing slash so that sync knows that this | ||
| 103 | > are directories. | ||
| 104 | |||
| 105 | I am planning to implement some sort of a `.ignore` file that will enable me to | ||
| 106 | have a project-specific exclude options. | ||
| 107 | |||
| 108 | I am currently running this every hour as a cronjob which is perfectly fine for | ||
| 109 | now when I am testing how this whole thing works and how it all will turn out. | ||
| 110 | |||
| 111 | I have also created a small Gnome extension which is still very unstable, but | ||
| 112 | when/if this whole experiment pays of I will share on Github. | ||
