Set up Fleek/Forestry staging and deploy flow #37

New Issue

2026-10-05T05:10:47+02:00

adam commented

2026-10-05 05:10:47 +02:00

Confirmed with @andyschwab that the plan is to deploy the new blog via Fleek rather than our own cluster. Next steps on this are as follows ...

@jdiogopeixoto, can you please set up a free Fleek account for deploying this repo? (Unfortunately, Fleek's permissioning isn't granular enough at the moment for me to be able to add you to the PL Fleek without giving you admin access to ALL PL sites, sigh.)
We'll need to set it up with main as the production branch, but I believe also to build deploy previews for all pull requests so we can preview other branches (see below).
Please set up Forestry to write to a new staging branch instead of main — I think that Fleek will still build deploy previews for changes made to staging, but we will need to confirm. (This staging vs main is the methodology currently being used for the Filecoin blog, so we want to be consistent.)

Once we confirm the above works (main successfully deployed via Fleek, plus updates to staging being visible to blog post authors), will need to do the following:

Move Fleek config over to PL Fleek account (could use .fleek.json config method)
Remove existing Netlify deploy workflow (I believe @andyschwab has access to this; I don't)

Confirmed with @andyschwab that the plan is to deploy the new blog via Fleek rather than our own cluster. Next steps on this are as follows ... - [x] @jdiogopeixoto, can you please set up a free Fleek account for deploying this repo? (Unfortunately, Fleek's permissioning isn't granular enough at the moment for me to be able to add you to the PL Fleek without giving you admin access to ALL PL sites, sigh.) - [x] We'll need to set it up with `main` as the production branch, but *I believe* also to build deploy previews for all pull requests so we can preview other branches (see below). - [x] Please set up Forestry to write to a new `staging` branch instead of `main` — I *think* that Fleek will still build deploy previews for changes made to `staging`, but we will need to confirm. (This `staging` vs `main` is the methodology currently being used for the Filecoin blog, so we want to be consistent.) Once we confirm the above works (`main` successfully deployed via Fleek, plus updates to `staging` being visible to blog post authors), will need to do the following: - [x] Move Fleek config over to PL Fleek account (could use [.fleek.json ](https://docs.fleek.co/hosting/site-deployment/#file-configuration)config method) - [x] Remove existing Netlify deploy workflow (I believe @andyschwab has access to this; I don't)

adam closed this issue

2026-10-05 05:10:47 +02:00

adam commented

2026-10-05 05:10:48 +02:00

Closing this issue, with summary noted below. We may wish to tweak this workflow over time as our ongoing use cases become more distinct. CCing @andyschwab for context.

PL Fleek account now has two "sites" for the blog:
- https://ipfs-blog-staging.on.fleek.co/ reflects the current state of the staging branch (to which Forestry writes changes directly) and is intended as staging preview
- https://ipfs-blog.on.fleek.co/ reflects the current state of the main branch and is intended to be what we point DNS at for blog.ipfs.io
Netlify "site" deploying from the current state of staging has been disabled, though we may wish to re-enable it if password protection is needed (see below)

Notes:

This does mean that viewing the staging environment is not password-protected, because Fleek doesn't currently support auth. Note that staging previews on the existing IPFS blog (hosted on our own cluster) aren't password-protected either, BUT if auth is determined necessary, we can switch back to deploying the staging environment via Netlify.
We'll need to remember to remove Forestry users' ability to write directly to main before go-live (it's helpful to keep around until then for expediency); added a note to that effect in https://github.com/ipfs/ipfs-blog/issues/22.
If blog posting becomes especially frequent, we may run into cases where simply PRing from staging to main results in needing to massage a particular PR in order to not merge in in-flight work. Acknowledging this as still a potential open issue.

Closing this issue, with summary noted below. **We may wish to tweak this workflow over time as our ongoing use cases become more distinct. CCing @andyschwab for context.** - PL Fleek account now has two "sites" for the blog: - https://ipfs-blog-staging.on.fleek.co/ reflects the current state of the `staging` branch (to which Forestry writes changes directly) and is intended as staging preview - https://ipfs-blog.on.fleek.co/ reflects the current state of the `main` branch and is intended to be what we point DNS at for blog.ipfs.io - Netlify "site" deploying from the current state of `staging` has been disabled, though we may wish to re-enable it if password protection is needed (see below) Notes: - This does mean that viewing the staging environment is not password-protected, because Fleek doesn't currently support auth. Note that staging previews on the existing IPFS blog (hosted on our own cluster) aren't password-protected either, BUT if auth is determined necessary, we can switch back to deploying the staging environment via Netlify. - We'll need to remember to remove Forestry users' ability to write directly to `main` before go-live (it's helpful to keep around until then for expediency); added a note to that effect in https://github.com/ipfs/ipfs-blog/issues/22. - If blog posting becomes especially frequent, we _may_ run into cases where simply PRing from `staging` to `main` results in needing to massage a particular PR in order to not merge in in-flight work. Acknowledging this as still a potential open issue.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/ipfs-blog#37