Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Very nice. I would recommend using putty to forward a local port to the server’s web control port so you can securely access the web without anyone between you and the server getting your login credentials.
@Morthawt: Great idea! We have an article on doing that here: <a href=“https://www.digitalocean.com/community/articles/how-to-set-up-ssh-tunneling-on-a-vps”>https://www.digitalocean.com/community/articles/how-to-set-up-ssh-tunneling-on-a-vps</a>.
Awesome post! We’d love to feature this on BitTorrent’s company blog. If you’re interested, please shoot me an email at kathie at bittorrent.com
Great post.
I do have a question about configuration though. I’m running Ubuntu 13.10, and I’ve installed btsync (not desktop) on two machines for testing purposes. File sync does occur, and as you indicate, btsync becomes owner/group for sync’d files on the server (default instance) and clients (and vice-versa). However, sync’d files are now read-only. Your graphic and text note this when you say “As you can see, the files are given to the btuser and group. This is because the service can’t be sure that the original username exists on the second system. This is not a problem and we can edit these files easily.” What exactly do you mean by this? My interpretation is that I SHOULD be able to edit (write) these files, but I’m seeing R-- for permissions (as your graphic points out), which would make editing impossible.
What am I missing?
Thanks much.
@richbl: See the <strong>Add Your User to the btsync Group and Give the Root User Ownership</strong>section.
richbl: Thanks for the heads up! I definitely forgot the step to configure the default umask of the daemon.
I’ve added the information to reconfigure the daemon with the correct umask settings which will allow the daemon to give the “btsync” group write permissions to any file that is synced.
@Kamal: Yeah, did that initially (I followed the full procedure), still having the issue described. In the tutorial, the permission flags clearly show read-only for group. So I’m confused as to how it’s possible to edit such a file unless you’re either owner or root. Maybe the procedure implies that you’re root.
@jellingwood: Just crossed posts with Kamal. I’ll take a look at the umask configuration. That might explain what I’m seeing. Thanks.
@jellingwood: The additional section on making a change to the btsync daemon did the trick. I didn’t realize that the dconf reconfiguration had additional settings lurking about.
Thanks again.