There is also this ticket: https://github.com/numenta/nupic.tools/issues/166
This is a much more generic ticket to add email sending capability to the tooling server. It might be a good place for a new contributor to start. (And I'll definitely start using it right away.) --------- Matt Taylor OS Community Flag-Bearer Numenta On Tue, Apr 14, 2015 at 9:16 AM, Matthew Taylor <[email protected]> wrote: > Hello NuPIC, > > Some of you have some JavaScript experience. It just so happens that > the most crucial part of the NuPIC build and deployment pipeline > (apart from GitHub and Travis-CI) is a tooling server written in > JavaScript on Node.js. > > Deployed: http://issues.numenta.org:8081/status > Source code: https://github.com/numenta/nupic.tools > > But there's a huge problem with it, and I need help to fix it. If > you're interested in helping out, read on! > > # The Problem > > This server is currently deployed on AWS EC2 under a private account. > I'm the only one with access to it. I don't like this, because I want > to give other community members permissions to make changes and > redeploy. Currently, redeployment takes a manual SSH to the box, > pulling the latest from git, and running a restart script. > > # The Solution > > I would much rather have this server deployed on Heroku so I could add > other community members as administrators. It's also really easy to > deploy new changes on Heroku using git. This is how I currently deploy > our wallboard at http://status.numenta.org/. > > # The *Real* Problem > > The tooling server has local checkouts of several repositories, and it > actually calls out to the shell to execute git commands. This is how > we deploy docs onto numenta.org whenever code gets merged in nupic, > nupic.core, or htm.java. This is also how automated pull requests like > https://github.com/numenta/nupic/pull/2054 are created against NuPIC > whenever nupic.core is updated. > > You can't have other git clones on Heroku, so I can't move it over > as-is. But if we could prevent these shell calls and local repository > checkouts (perhaps by using the GitHub Git Data API), then we could > move to Heroku. I have tickets filed for this work: > > - https://github.com/numenta/nupic.tools/issues/175 > - https://github.com/numenta/nupic.tools/issues/176 > > > So if anyone is interested in helping, please let me know and I'll > guide you along. The tooling server is a bit complicated (sorry), and > it plays a lot of roles. It's kindof a kitchen sink tooling app. I'm > pretty much the only person who's written code for it, and you know > how code can get when there's only one person working on it. ;) It > could definitely use some TLC. > > --------- > Matt Taylor > OS Community Flag-Bearer > Numenta
