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
I am using Gatsby to create a CMS where users can author articles. The backend lives on AWS and is mostly event driven.
My naive implementation is to periodically run a gatsby build, query all published articles, and then rebuild all article HTML from template. This involves great duplication of effort for any non-new articles (which are rarely, if ever, changed and therefore whose HTML does not change).
It seems like the Gatsby-recommended way to remediate unnecessary build effort is to use Incremental Builds. However, this seems to still rely heavily on checking a cache to look for diffs throughout the app. Also, at this early stage I'm not clear on where this cache is intended to live.
Alternatively, is it possible to ingest an article publish event, build the HTML with just that data and the appropriate template (e.g. call createPage(myNewArticleData), and then append that HTML to the pre-existing Gatsby build package (in this case, an S3 bucket)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am using Gatsby to create a CMS where users can author articles. The backend lives on AWS and is mostly event driven.
My naive implementation is to periodically run a
gatsby build
, query all published articles, and then rebuild all article HTML from template. This involves great duplication of effort for any non-new articles (which are rarely, if ever, changed and therefore whose HTML does not change).It seems like the Gatsby-recommended way to remediate unnecessary build effort is to use Incremental Builds. However, this seems to still rely heavily on checking a cache to look for diffs throughout the app. Also, at this early stage I'm not clear on where this cache is intended to live.
Alternatively, is it possible to ingest an article publish event, build the HTML with just that data and the appropriate template (e.g. call
createPage(myNewArticleData)
, and then append that HTML to the pre-existing Gatsby build package (in this case, an S3 bucket)?Beta Was this translation helpful? Give feedback.
All reactions