The Uploader
Optional · sends the Downloader's media to logrrrWhat it does
The Uploader runs on the same computer as the Downloader. It sends the media the Downloader saved up to logrrr, where it appears with each event in your console. logrrr checks every upload arrived intact before it counts it.
It's the part that talks to logrrr, so it needs an uploader API key. It doesn't use your console password.
Get an uploader key
- Sign in to the console and open Settings → API keys. You need to be an owner, admin or tech of the account.
- Under Create a key, choose Uploader, give it a name (for example the computer's name), and choose Create key.
- Copy the key now. The console shows the whole key only this once. If you lose it later, choose Regenerate to get a new one.
Add it to LogrrrSettings
Once Step 1 (the Downloader's connection) succeeds, the Getting Started tab shows Step 2: Connect Your Logrrr Account. Paste the key into Uploader API Key and choose Save API Key. LogrrrSettings stores it encrypted on this computer and restarts both services.
You can also paste a key on the Uploader Settings tab. Saving there doesn't restart anything, so restart the Uploader service afterwards from the Uploader Service tab. The Uploader reads its key only when it starts.
Check it's working
In the console, Settings → API keys shows when each key was last used. An uploader key used in the last few minutes means the Uploader is running and signing in. If a key that used to be active hasn't been used for over a day, the console flags it.
Events with uploaded media show the extra files on their event page.
Moving to a new computer
Install on the new computer, then in the console choose Regenerate on the old uploader key and paste the new key into LogrrrSettings (Getting Started Step 2 restarts the services for you). The old key stops working straight away, so the old computer can't keep uploading.
Logs
The Uploader writes one log file a day to Logs\LogrrrUnifiProtectUploader_YYYY-MM-DD.log inside the media folder. See log files and troubleshooting.