Paras Singh Laddi

We're on Java version 1.8 currently

@MatthewHartstonge I tried deploying to heroku using the `package.json` edit. Unfortunately it didn't work. So I proceeded on with the recommended `Procfile`. ``` web: node main.js facebook ``` **PS**: Logging...

@mrkno Thanks for the heads-up! I might look into alternative solutions

Currently, the **Procfile** is not being detected by Heroku and I don't know why and I've managed to utilize `package.json` to modify how Concierge is ran (If no **Procfile** is...

I've pinpointed the issue about why **Procfile** wasn't detected. ~~The `node-buildpack` that comes with heroku has `web` as it's primary configuration~~ I think Heroku sets `web` as primary configuration for...

@mrkno I just noticed all modules are installed in /tmp directory by default for r/w access and I didn't had to specify it manually. So it does partially persist right...

@mrkno You are right. They are indeed being moved to `/app/modules` after cloning into `/tmp`. And no, modules fail to install if they `require` some module from npm :( >...

I'm wondering if using the dyno's `config vars` for Concierge's persistence will be a good idea. The variables remain persistent across restarts and can be accessed via `process.env`. A simple...

@mrkno I've decided to write a service that makes a `git commit` to `heroku`'s local git repo every time a file is changed. Still WIP [here](https://github.com/concierge/heroku-service). A problem now is...

Yikes! Looks like the mountain of problems in `heroku` are far too many. I might stop pursuing a persistent build if the current plan doesn't works out. Thanks for the...