Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Application Distribution
JavaScript CSS Shell
Branch: hurpdurp
#1 Compare This branch is 3 commits ahead, 5 commits behind SpotterRF:master.

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.

Controlling The HurpDurp Apps Server


The first thing you'll need to do in order to use the HurpDurp Apps Server is install it. Use one of our patented automagic install applications on your platform of choice. We support Linux, Macintosh OS X, and Windows 7.


Restarting the server, and you.

To restart the local server, you'll need to run these two commands, in order:

sudo launchctl unload /Library/LaunchDaemons/com.hurpdurp.apps.plist
sudo launchctl load /Library/LaunchDaemons/com.hurpdurp.apps.plist

Deleting applications, and you.

To delete an application, you will need to manually remove the files that were installed with that application. All applications that Appr installs, are located under /usr/local/lib/hurpdurp/mounts/. You'll be able to find apps, such as the Tracker Display installed there. To delete one of these apps, simply run the following command:

sudo rm -rf /usr/local/lib/hurpdurp/mounts/appName

Be sure to replace appName with the name of the app you want to delete. Otherwise, you may run into problems down the line.

After the app is removed, you will need to restart the patented SpotterRF Apps server. To perform this action, please refer to the information above.

Publishing applications, and you.

Boy skippy, it couldn't be more easy to publish applications to the Appr store. Follow this easy 12 step process to publish an app:

  1. Login to your trusty sidekick server.
  2. Create a ~/src directory, if you haven't already.
  3. Copy your application files to a directory named ~/src/app-name.
  4. Change directory into ~/src/app-name
  5. Run any applicable build scripts.
  6. Create a package.json if you haven't already.
  7. Add publishConfig: { "registry": "http://your-npm-registry" } to package.json
  8. Add the line registry = http://your-npm-registry to your ~/.npmrc
  9. Run npm adduser --registry=http://user:pass@your-npm-registry and follow the steps.
  10. Make sure you're in the ~src/app-name directory.
  11. Run npm publish ./

Grand Plan

The idea is to have an app store similar to the android app store.

  • Appr represents the app store client
  • represents the default

Installation as entrypoint

  1. I visit
  2. checks localhost:8899/oauth and fails
  3. asks me for a username and password for hurpdurp
  4.'s client creates a ticket for with
  5. asks me to install Appr from{exe,pkg,deb}
  6. continually polls localhost:8899/init/:ticket

Appr setup via

  1. Appr is installed
  2. Appr has no config, so it listens on localhost:8899/init/:ticket
  3. Appr receives the ticket
  4. Appr checks
  5. only responds when the Origin is localhost:8899
  6. the response passes credentials (the user is pre-logged in on localhost and is pre-authorized) as app

  1. I visit again
  2. checks localhost:8899/oauth and has succeeds with pre-authorization, pre-scoped
  3. I enjoy as new app

  1. I visit
  2. checks localhost:8899/oauth and succeeds
  3. A list is presented including hurpdurp,, etc
  4. I authorize for whichever scope
  5. is added to the list of repos


  1. Appr checks regularly for the latest node version and date
  2. Appr checks each app at to get a list of compatible app versions
  3. If all apps have compatible versions at or above their current version, the upgrade takes place


  1. Going to directly will show a list of authorized apps from localhost:8899, which accepts as a master (not just a repo)


Apps should have a

  • version
  • install date
  • upgraded date
  • channel (stable, beta, developer (only selectable via api))
  • scope
  • origin (install source url)
Something went wrong with that request. Please try again.