67cde92f64
Bumps [node-fetch](https://github.com/bitinn/node-fetch) from 2.3.0 to 2.6.1. - [Release notes](https://github.com/bitinn/node-fetch/releases) - [Changelog](https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md) - [Commits](https://github.com/bitinn/node-fetch/compare/v2.3.0...v2.6.1) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
---|---|---|
lib | ||
public | ||
routes | ||
views | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
Dockerfile | ||
Dockerfile-PROD | ||
LICENSE | ||
README.md | ||
app.js | ||
docker-compose.yml | ||
field_config.json | ||
index.js | ||
package-lock.json | ||
package.json |
README.md
Mozilla Fenix Campaign
Campaign Bug Reporting page for the upcoming Fenix Campaign lead by the Open Innovation Team.
Setting up the server
Requirements
- First install Docker and docker-compose
- Create a repository to hold the submitted issues
- Create a "triage" label for issues in that repository
- Create a personal access token for your GitHub user
Starting
Then you can start the server with the following command. Make sure to replace the placeholders with your data.
$ git clone <URL>
$ cd fenix-campaign
$ npm install
$ GITHUB_TOKEN=<yourGitHubToken> OWNER=<yourGitHubUsername> REPO=<yourGitHubRepoForIssues> npm start
Now you can access the website for it at localhost:4000
.
Note: When running locally, screenshots won't be appended to the resulting GitHub Issue
Without Docker
If you wanna use it without docker, you can run it by:
$ git clone <URL>
$ cd fenix-campaign
$ npm install
$ GITHUB_TOKEN=<yourGitHubToken> OWNER=<yourGitHubUsername> REPO=<yourGitHubRepoForIssues> SESSION_SECRET=someSECRET BASE_URL=http://localhost:4000 node index