81b7eeeb71
* Re-organize common folder * fix: Correct paths in tests * fix: move new content to proper folder * chore: Move audio folder to assets * Move sprites to sprites assets directory * Move css sprites to assets directory * Split out readmes for common code and sprites * Move images to assets directory * Move destinatin of shared browserified file * remove unused file * move compiled js to client-old * Fix karma tests * fix: Correct paths for sprites |
||
|---|---|---|
| .ebextensions | ||
| .github | ||
| database_reports | ||
| debug-scripts | ||
| dist | ||
| keys/google | ||
| migrations | ||
| scripts | ||
| tasks | ||
| test | ||
| vagrant_scripts | ||
| website | ||
| .babelrc | ||
| .bowerrc | ||
| .buildpacks | ||
| .codeclimate.yml | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .nodemonignore | ||
| .nvmrc | ||
| .travis.yml | ||
| apidoc.json | ||
| bower.json | ||
| config.json.example | ||
| docker-compose.dev.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Gruntfile.js | ||
| gulpfile.js | ||
| karma.conf.js | ||
| LICENSE | ||
| npm-shrinkwrap.json | ||
| package.json | ||
| Procfile | ||
| README.md | ||
| VAGRANT.md | ||
| Vagrantfile.example | ||
Habitica 
Habitica is an open source habit building program which treats your life like a Role Playing Game. Level up as you succeed, lose HP as you fail, earn money to buy weapons and armor.
We need more programmers! Your assistance will be greatly appreciated.
For an introduction to the technologies used and how the software is organized, refer to Contributing to Habitica - "Coders (Web & Mobile)" section.
To set up a local install of Habitica for development and testing, see Setting up Habitica Locally, which contains instructions for Windows, *nix / Mac OS, and Vagrant.
Then read Guidance for Blacksmiths for additional instructions and useful tips.
Debug Scripts
In the ./debug-scripts/ folder, there are a few files. Here's a sample:
grant-all-equipment.js
grant-all-mounts.js
grant-all-pets.js
You can run them by doing:
node debug-scripts/name-of-script.js
If there are more arguments required to make the script work, it will print out the usage and an explanation of what the script does.