#Resilio sync on shared host install#
#Resilio sync on shared host android#
#Resilio sync on shared host code#

The last step required for a fully functional feed reader is creating a cronjob to refresh the feeds at a specified interval. Don’t forget to create a new user and change the administrative password! The default username and password is: admin/password. This will create a config.php file in the root of the main application directory.

#Resilio sync on shared host code#

Now you should be presented with a textbox containing the php configuration code required to run tt-rss. Admittedly, the setup process of tt-rss it’s a bit quirky.įill the configuration form with the information provided during the db creation stage.Ĭlick on the “Test Configuration” button to double-check you can access the database and all required libraries are present. The first time you hit the url ‘’, a set-up page is displayed. Mysql> grant all on ttRssDB.* to identified by 'password' The set-up process is similar to the one used for the other applications. There are lots of self-hosted feed readers out there: I have tried few of them, and I settled with tt-rss. Tiny Tiny RSS (tt-rss for brevity) is a marvellous feed reader, which I use daily.

#Resilio sync on shared host android#

Bonus: SQLite is easier to backup!Īs an Android user, I use CardDAV-Sync to syncronize my contacts and CalDav-Sync for the calendar syncronization. I have around 1000 contacts and a relatively low number of entries in my calendars and never had a problem. I don’t bother creating a MySQL db for Baikal. If you choose MySQL, you’ll have to create a database first. Hit on your browser and you should access the configuration page.Ĭhoose an admin password and pick MySQL or SQLite.

It is assumed that the server IP address is associated to a DNS entry and that all the applications have a sub domain, like so: Resilio Sync (formerly known as BitTorrent Sync)Īll the web-facing applications use HTTPS (thanks Let’s Encrypt!).

#Resilio sync on shared host install#

The configuration process described here is based on Ubuntu 16.04 LTS and does install and configure the following applications: At this point (end of 2016), my digital backbone is almost completely self-hosted, except for an e-mail server, which I happily leave to Fastmail. I started to look for a self-hosted alternative to Dropbox back in 2013, mostly out of privacy concerns, and I continued to add more self-hosted applications to my server ( a 4GB RAM box hosted with Hetzner).

Having said that, with a relatively small time-investment, I have never suffered any major (or minor) data-loss or data breach. On the other hand, self-hosting forces you to be very proactive about your data, chiefly:īoth back-up and security are not easy feat to get right, so self-hosting requires a certain degree of discipline. There are plenty of reasons you want to self-host applications (privacy, who owns your data, your data being stolen, etc.). These notes contain a relatively simple guide to set-up a fresh Ubuntu server and self-host a number of ( what I consider) essential apps.