Move to toolforge build-service #13
Conversation
|
For context, this package isn’t primarily designed to be a MediaWiki bot like the other projects you’ve opened similar PRs against. However, it was being run on a cron job on Toolforge as a lightweight service: #2 (comment). I’m fine with the requested changes and appreciate your help in getting that service back up and running, but the changes need to avoid impacting other environments such as Web applications. |
This adds: * Procfile + web.sh to run the web server * Aptfiles with python as a dependency to serve static files * http-server module to serve the generated json files * Used the $TOOl_DATA_DIR in build.js to generate the files in the right path. * Added info in the readme Signed-off-by: David Caro <[email protected]>
|
Feel free to ping me if someone wants access to wmf-sitematrix.toolforge.org. I moved all my projects off Toolforge a while back but I could see why others would like this back on WMF infrastructure. |
| @@ -11,7 +11,7 @@ var projects = [ | |||
| ]; | |||
|
|
|||
| var fs = require('fs'); | |||
| let dataPath = "data"; | |||
| let dataPath = `${process.env.TOOL_DATA_DIR}/public_html/data`; | |||
There was a problem hiding this comment.
I missed this at the time, but TOOL_DATA_DIR is normally undefined when running the update script locally. 9d842c6 makes this environment variable optional.
This adds: