From 837a34cf71ee7eb2c4c2e758cefd6ddfef2bb554 Mon Sep 17 00:00:00 2001 From: Leo Lamprecht Date: Sat, 12 Aug 2017 12:44:21 +0200 Subject: [PATCH] Indicate that Nuts supports private repositories --- docs/tutorial/updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/updates.md b/docs/tutorial/updates.md index bd3d5d345a7..48a6b0fb469 100644 --- a/docs/tutorial/updates.md +++ b/docs/tutorial/updates.md @@ -9,7 +9,7 @@ To get started, you firstly need to deploy an update server (that's where the [a Depending on your needs, you can choose from one of these: - [Hazel](https://github.com/zeit/hazel) – Pulls new releases from [GitHub Releases](https://help.github.com/articles/creating-releases/) and is **perfect for getting started** -- [Nuts](https://github.com/GitbookIO/nuts) – Also uses [GitHub Releases](https://help.github.com/articles/creating-releases/), but caches app updates on disk +- [Nuts](https://github.com/GitbookIO/nuts) – Also uses [GitHub Releases](https://help.github.com/articles/creating-releases/), but caches app updates on disk and supports private repositories - [electron-release-server](https://github.com/ArekSredzki/electron-release-server) – Provides you with a dashboard for handling releases ## Implementing Updates into Your App