You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/README.md
+14-5Lines changed: 14 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -177,7 +177,7 @@ It is possible to run the Super-Linter locally if you have Docker installed.
177
177
First up pull the Super-Linter Docker image (this takes some time to download but only need to do this once or when you want to upgrade the version of the super-linter):
178
178
179
179
```
180
-
docker pull github/super-linter:latest
180
+
docker pull github/super-linter/slim:latest
181
181
```
182
182
183
183
Then to run the linting do this:
@@ -253,7 +253,7 @@ To actually generate the ebooks, start your local server, then run the following
253
253
npm run ebooks
254
254
```
255
255
256
-
There is a GitHub Action which can be run manually from the Actions tab to generate the Ebooks and open a Pull Request for them. This is the easiest way to generate them.
256
+
There is a GitHub Action which can be run manually from the Actions tab to generate the Ebooks and store the resulting files in an artifact. This is the easiest way to generate them.
257
257
258
258
## Generating ebooks - including print-ready ebooks if you want a hardcopy
259
259
@@ -291,7 +291,7 @@ This is the same as below since it uses all the default settings:
291
291
prince "http://127.0.0.1:8080/en/2019/ebook?print&printer&page-size=A5&inside-margin=19.5mm&bleed=3mm&prince-trim=5mm&base-font-size=10px" -o static/pdfs/web_almanac_2019_en_print_A5.pdf
292
292
```
293
293
294
-
Note this will create two extra pages at the begining which will need to be removed with a PDF editor (e.g. Adobe Acrobat) to start with a clean page starting on right hand side for printing. Please remove these before checking in versions into git.
294
+
Note this will create two extra pages at the begining which will need to be removed with a PDF editor (e.g. Adobe Acrobat) to start with a clean page starting on right hand side for printing. Please remove these before deploying.
295
295
296
296
It is also possible to generate a cover using the `&cover` URL param. This consists of basically 2 pages - the first page is a double width-page with front and back cover as one page (with spine in between) and the second page is a blank inside page.
297
297
@@ -332,6 +332,14 @@ You must first do some setup locally:
332
332
gcloud init
333
333
```
334
334
335
+
3. Set Github personal access token to GITHUB_TOKEN environment variable
336
+
337
+
Use an existing token or create a new token [in GitHub.com](https://github.com/settings/personal-access-tokens/new). In token configuration select *Repository access = Public Repositories (read-only)*.
338
+
339
+
```bash
340
+
export GITHUB_TOKEN=...
341
+
```
342
+
335
343
### Deploying staged versions of the site
336
344
337
345
It's sometimes useful to deploy a staged version of the site for others to see this.
@@ -360,8 +368,9 @@ The deploy script will do the following:
360
368
- Ask you to confirm you've run the pre-deploy script via GitHub Actions
361
369
- Switch to the production branch
362
370
- Merge changes from main
363
-
- Do a clean install
364
-
- Run the tests
371
+
- Do a clean install (remove generated chapters and e-books)
372
+
- Download latest e-books from Github Action artifacts
373
+
- Run and test the website
365
374
- Ask you to complete any local tests and confirm good to deploy
366
375
- Ask for a version number (suggesing the last verision tagged and incrementing the patch)
367
376
- Tag the release (after asking you for the version number to use)
0 commit comments