This project is dead, unfortunately.

We're keeping it here as a monument and potential source of inspiration.

--

galleon

Galleon will be VLACS' competencies-centric education tracking system.

Dev/Test Workflow

1. Clone this repo, and cd into the repo directory.
2. Get immutant if you don't have it yet.
   1. Run lein immutant install. (The immutant plugin dep is in project.clj.)
3. Add [lein-voom "0.1.0-20140520_203433-gc1e2883" :exclusions [org.clojure/clojure]] to your :plugins in ~/.lein/profiles.clj. For example, this should work: {:user {:plugins [[lein-voom "0.1.0-20140520_203433-gc1e2883" :exclusions [org.clojure/clojure]]]}}
   1. Run lein voom freshen to get the latest commits for helmsman, dossier, etc.
   2. Run lein voom build-deps to pull and build those dependencies and install them in your ~/.m2/ tree.
4. cp galleon-conf-dist.edn galleon-conf.edn
5. Edit galleon-conf.edn as necessary.
6. Deploy galleon to immutant: lein immutant deploy
7. Start up immutant in another terminal with lein immutant run. Watch for the nREPL connection port for your deployment of galleon, though immutant sets .nrepl-port in your project root dir correctly so this isn't essential.
   1. Connect from the CLI: lein repl :connect (automatically uses .nrepl-port)
   2. Connect from emacs: M-x cider and accept the defaults.
8. Test your nREPL to be sure you're in immutant: (util/in-immutant?)
9. immutant/init.clj initializes the project, so it's already running. But you can (reset) it if you like:
   1. (reset) will reload your code without deleting the Datomic database.
   2. (reset-and-delete-db! :delete-db) will reload your code AND DELETE THE DATOMIC DATABASE.
10. See REPL-code examples in (comment ...) in dev/user.clj.

Running tests

You can build the necessary dependencies for galleon and run the tests at the same time.

$ ./test.sh

Browser path

Note that the app deploys to /galleon/ to allow for multiple apps to be deployed in one immutant.

Using the queues

The queues in the gangway namespace use token based authentication, so you must include an Authorization header with your HTTP request.

  Authorization: Token thisiswhereyourtokengoes

In order your requests to go through you must generate a token for yourself. Theres a handy function for this available from the repl in the user namespace.

Fire up the application, then connect to it with your REPL, once connected you should be able to run:

  user=> (add-queue-token! "Owner Name" 3) 

The 3 in the above command represents the number of months before the token expires.

Once you have your token you can send JSON requests to any of the queue endpoints.