Files
shields/app.json
Paul Melnikow c5e31b5de1 Fix frontend deploy and Heroku staging (#1288)
- Heroku reads the Node version from package.json. We're about to upgrade to Node 8 so this change to `engines` is only pre-emptive. It won't have any effect on the production servers.
- The production deploy scripts were missing the frontend files. This fixes that.
- This modifies the build setup to allow `BASE_URL=/`, which makes all requests relative to the page itself. That simplifies deploying the "debugging" frontend to the production servers, and makes it easy to host the frontend on Heroku.
2017-11-29 17:59:01 -05:00

30 lines
688 B
JSON

{
"name": "Shields",
"description": "Concise, consistent, and legible badges in SVG and raster format.",
"keywords": [
"badge",
"github",
"svg",
"status"
],
"website": "https://shields.io/",
"repository": "https://github.com/badges/shields",
"logo": "http://shields.io/favicon.png",
"env": {
"NPM_CONFIG_PRODUCTION": {
"description": "Configure whether devDependencies are installed (they are needed for the build).",
"value": "false"
},
"BASE_URL": {
"description": "The base URL to use in the frontend build",
"value": "/"
}
},
"formation": {
"web": {
"quantity": 1,
"size": "free"
}
}
}