Gods help us all.
$ brew install redis $ brew install node
This will install both of the requirements. The remaining requirements will be installed by the application layer.
Tech Stack and Tech Stack Accessories
- We use Sass as the CSS language, and CSS is stored in /assets/css in the repository, served at
- We use Handlebars templates, in /views running inside the
mainlayout in /views/layouts
- Handlebars integration is provided with the express-handlebars package
- Anything placed in /public is accessible on the site as
- The production site runs in Heroku
That's about it. If something is stupid or confusing, FILE A FUCKING ISSUE so that it can get fixed.
First, clone the repository, and set the name of the remote to
upstream. This will become useful when you fork the repository to contribute changes.
$ git clone https://github.com/desert-planet/ayp $ cd ayp $ git remote rename origin upstream
Now use npm, which should have been installed with node, to install the application and all of its dependencies.
$ npm install
If nothing goes wrong, you can then load the local database with some test strips after loading the dev environment.
$ . script/ayp-env $ script/db-seed => I'm gonna stuff your DB with some content. [..snip..]
Now you're GOOD TO GO. To run the development server
$ npm start Your pants running at http://localhost:5000/
If you wish to see your changes reloaded on the server, use
npm run watch
Setting up your fork for contribution
If you have already created a fork, you can add that remote as
$ git remote add origin https://github.com/your_name_here/ayp
So that newly created branches will push to your fork, but switching to
master and running
git pull will get the latest changes from the upstream repository.