Open this link in a new tab to deploy Hazel on Vercel:
Once it's deployed, paste the deployment address into your code (please keep in mind that updates should only occur in the production version of the app, not while developing):
From now on, the auto updater will ask your Hazel deployment for updates!
Options
The following environment variables can be used optionally:
INTERVAL: Refreshes the cache every x minutes (restrictions)
PRE: When defined with a value of 1, only pre-releases will be cached
TOKEN: Your GitHub token (for private repos)
URL: The server's URL (for private repos - when running on Vercel, this field is filled with the URL of the deployment automatically)
Statistics
Since Hazel routes all the traffic for downloading the actual application files to GitHub Releases, you can use their API to determine the download count for a certain release.
As an example, check out the latest Hyper release and search for mac.zip. You'll find a release containing a sub property named download_count with the amount of downloads as its value.
Routes
/
Displays an overview page showing the cached repository with the different available platforms and file sizes. Links to the repo, releases, specific cached version and direct downloads for each platform are present.
/download
Automatically detects the platform/OS of the visitor by parsing the user agent and then downloads the appropriate copy of your application.
If the latest version of the application wasn't yet pulled from GitHub Releases, it will return a message and the status code 404. The same happens if the latest release doesn't contain a file for the detected platform.
/download/:platform
Accepts a platform (like "darwin" or "win32") to download the appropriate copy your app for. I generally suggest using either process.platform (more) or os.platform() (more) to retrieve this string.
If the cache isn't filled yet or doesn't contain a download link for the specified platform, it will respond like /.
/update/:platform/:version
Checks if there is an update available by reading from the cache.
If the latest version of the application wasn't yet pulled from GitHub Releases, it will return the 204 status code. The same happens if the latest release doesn't contain a file for the specified platform.
/update/win32/:version/RELEASES
This endpoint was specifically crafted for the Windows platform (called "win32" in Node.js).
Since the Windows version of Squirrel (the software that powers auto updates inside Electron) requires access to a file named "RELEASES" when checking for updates, this endpoint will respond with a cached version of the file that contains a download link to a .nupkg file (the application update).
Programmatic Usage
You can add Hazel to an existing HTTP server, if you want. For example, this will allow you to implement custom analytics on certain paths.
Fork this repository to your own GitHub account and then clone it to your local device
Move into the directory of your clone: cd hazel
Install Vercel CLI and run the development server: vercel dev
Credits
Huge thanks to my (@leo's) friend Andy, who suggested the name "Hazel" (since the auto updater software inside Electron is called "Squirrel") and Matheus for collecting ideas with me.