You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Eric Ihli dadbb78c37 Update README with citations 3 years ago
db Add README and update migration code 3 years ago
kv Add notes for KV store 3 years ago
load-balancer Gitignore unneeded files 3 years ago
util Gitignore unneeded files 3 years ago
web Update README with citations 3 years ago
.dir-locals.el Add makefile for deploys 4 years ago
.gitattributes Add models to tracking 3 years ago
.gitignore Gitignore unneeded files 3 years ago
Makefile Add code related to rhyming and ssl 3 years ago
README.org Update README 3 years ago

README.org

RhymeStorm™

WGU Evaluator Notes

How To Initialize Development Environment

Steps

  1. Run ./db/run.sh && ./kv/run.sh to start the docker containers for the database and key-value store.

    1. The run.sh scripts only need to run once. They initialize development data containers. Subsequent development can continue with docker start db && docker start kv.
  2. Start a Clojure REPL in Emacs, evaluate the dev/user.clj namespace, and run (init)
  3. Visit http://localhost:8000/wgu

How To Run Software Locally

Requirements

Steps

  1. Run ./db/run.sh && ./kv/run.sh to start the docker containers for the database and key-value store.

    1. The run.sh scripts only need to run once. They initialize development data containers. Subsequent development can continue with docker start db && docker start kv.
  2. The application's jar builds with a make run from the root directory. (See Makefile).
  3. Navigate to the root directory of this git repo and run java -jar darklimericks.jar
  4. Visit http://localhost:8000/wgu

Development

Requires Tachyons CSS. There is a symlink in web/resources/public to the pre-built tachyons.css and tachyons.min.css found in the repo.

Build .jar with clojure -X:depstart uberjar :jar prhyme.jar.

TODO

Use tightly packed trie for limerick generation

Move limerick-specific code into this repo from Prhyme.

Or maybe into its own repo.