feat: integration tests for /dl/:filename

.github/workflows/cicd.yml

@@ -12,11 +12,15 @@ jobs:
       - name: Use Node.js ${{ matrix.node-version }}
         uses: actions/setup-node@v3
         with:
-          node-version: 16
+          node-version: 18
           cache: "npm"
       - run: npm ci
       # - run: npm run lint
       - run: npm test
+        env:
+          GITHUB_OWNER: owner-nock-mocked
+          GITHUB_REPO: repo-nock-mocked
+          GITHUB_TOKEN: token-nock-mocked
       - run: npm run build
       - run: npm run semantic-release
         env:

.mocharc.js

@@ -1,3 +1,4 @@
+/** @type { import('mocha').MochaInstanceOptions } */
 module.exports = {
   color: true,
   exit: true,

docs/deploy.md

@@ -2,19 +2,13 @@
 
 Pecans can be easily be deployed to a state-less server or PaaS. It only uses the disk as a cache for assets.
 
-### On Heroku:
+<!-- ### With docker
 
-Heroku is the perfect solution to host a Pecans instance.
+You'll need to build your own pecans image at this time. We do not net publish one.
 
-[![Deploy](https://www.herokucdn.com/deploy/button.png)](https://heroku.com/deploy)
-
-### With docker
-
-Pecans can also be run as a Docker container:
-
-```
-docker run -it -p 80:80 -e GITHUB_REPO=username/repo gitbook/pecans
 ```
+docker run -it -p 80:80 -e GITHUB_REPO=username/repo dopry/pecans
+``` -->
 
 ### On your own server:
 

env.test.sh

@@ -0,0 +1,4 @@
+# for pecans
+export GITHUB_OWNER="owner-nock-mocked"
+export GITHUB_REPO="repo-nock-mocked"
+export GITHUB_TOKEN="token-nock-mocked"