Compare commits
2 Commits
Author | SHA1 | Date | |
---|---|---|---|
|
78250bd9a2 | ||
|
5c0a4a2523 |
@@ -11,7 +11,7 @@ You can read more about how this project came about in my blog post '[Introducin
|
|||||||
- `src/index.html` - a [Nunjucks](https://mozilla.github.io/nunjucks/) template that lets you change how the feeds are displayed
|
- `src/index.html` - a [Nunjucks](https://mozilla.github.io/nunjucks/) template that lets you change how the feeds are displayed
|
||||||
- `output/style.css` - a CSS file to stylize your feed output
|
- `output/style.css` - a CSS file to stylize your feed output
|
||||||
- `src/feeds.json` - a JSON file containing the URLs for various site's feeds separated into categories
|
- `src/feeds.json` - a JSON file containing the URLs for various site's feeds separated into categories
|
||||||
- `src/index.js` - the script that loads the feeds and does the actual parsinga and rendering
|
- `src/index.js` - the script that loads the feeds and does the actual parsing and rendering
|
||||||
|
|
||||||
## Demos
|
## Demos
|
||||||
|
|
||||||
@@ -65,7 +65,7 @@ If you already have a server running Linux and some command-line experience it m
|
|||||||
|
|
||||||
#### Using GitHub Actions
|
#### Using GitHub Actions
|
||||||
|
|
||||||
This approach is a little different and requires some modifications to the repository. Netlify started billing for [build minutes](https://www.netlify.com/pricing/faq/) very shortly after I published this project. Running `npm build` and downloading all of the RSS feeds took up a substantial number of these, particulary if you had a process pinging the webhook and triggering a build every 15 minutes or so.
|
This approach is a little different and requires some modifications to the repository. Netlify started billing for [build minutes](https://www.netlify.com/pricing/faq/) very shortly after I published this project. Running `npm build` and downloading all of the RSS feeds took up a substantial number of these, particularly if you had a process pinging the webhook and triggering a build every 15 minutes or so.
|
||||||
|
|
||||||
How is the The GitHub Action-based approach different? The same build process runs, but this time it's on GitHub's servers via the Action. It then **commits** the newly created file generated at `./output/index.html` back into the repository. Netlify still gets pinged when the repository is updated, but skips the `npm run build` step on their end. This significantly reduces the number of build minutes required.
|
How is the The GitHub Action-based approach different? The same build process runs, but this time it's on GitHub's servers via the Action. It then **commits** the newly created file generated at `./output/index.html` back into the repository. Netlify still gets pinged when the repository is updated, but skips the `npm run build` step on their end. This significantly reduces the number of build minutes required.
|
||||||
|
|
||||||
|
@@ -14,6 +14,7 @@
|
|||||||
],
|
],
|
||||||
"My GitHub Projects": [
|
"My GitHub Projects": [
|
||||||
"https://github.com/georgemandis.atom",
|
"https://github.com/georgemandis.atom",
|
||||||
|
"https://github.com/georgemandis/bubo-rss/releases.atom",
|
||||||
"https://github.com/georgemandis/konami-js/releases.atom",
|
"https://github.com/georgemandis/konami-js/releases.atom",
|
||||||
"https://github.com/georgemandis/konami-js/commits/main.atom",
|
"https://github.com/georgemandis/konami-js/commits/main.atom",
|
||||||
"https://github.com/javascriptforartists/cheer-me-up-and-sing-me-a-song/commits/master.atom",
|
"https://github.com/javascriptforartists/cheer-me-up-and-sing-me-a-song/commits/master.atom",
|
||||||
@@ -21,4 +22,4 @@
|
|||||||
"https://github.com/georgemandis/remote-working-list/commits/master.atom",
|
"https://github.com/georgemandis/remote-working-list/commits/master.atom",
|
||||||
"https://github.com/georgemandis/tweeter-totter/commits/master.atom"
|
"https://github.com/georgemandis/tweeter-totter/commits/master.atom"
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
Reference in New Issue
Block a user