Switch hosting provider about website-metalsmith HOT 19 OPEN

I think we can switch to Netlify given (https://www.netlify.com/legal/open-source-policy) or Vercel (https://vercel.com/support/articles/can-vercel-sponsor-my-open-source-project).

Whatever you chose - I have contacts on both providers.

from website-metalsmith.

@luisorbaiceta if you include a badge https://www.netlify.com/press/#badges in the footer, I can request an OSS account from Netlify.

from website-metalsmith.

I would go ahead with Netlify unless somebody has a strong preference for something else. I don't know what would entail to pick Netlify vs something else (or roll our own). I'm just working to create a sponsored account for Fastify.

Do anyone have an objection in picking Netlify?

from website-metalsmith.

I have requested an OSS account from Netlify

from website-metalsmith.

As you prefer, you should have enough permissions for both - in case let me know.

from website-metalsmith.

@sinchang, in your experience with Netlify, do you think it could solve #312?

from website-metalsmith.

Really want to see this happen. It's very frustrating not being able to see how changes to docs in the main repo will affect the site without first merging into main.

from website-metalsmith.

Really want to see this happen. It's very frustrating not being able to see how changes to docs in the main repo will affect the site without first merging into main.

I'm afraid this is a consequence of the current build process and has nothing to do with the provider. A good solution would be to always work on the same branch the docs changes (wip/docs) and targeting that specific branch in the build process (like we do with master branch). We can leave that part hidden for the final user and only make it available by route access

from website-metalsmith.

I do not wish to complicate the core repo contribution workflow. The website build should be able to accommodate the normal PR process.

from website-metalsmith.

@luisorbaiceta it should be possible by triggering a rebuild using the API.

from website-metalsmith.

If changes have not been merged to master, there is no way to preview them without knowing the name of the branch those changes have been made in beforehand. See here

from website-metalsmith.

@luisorbaiceta if you include a badge https://www.netlify.com/press/#badges in the footer, I can request an OSS account from Netlify.

Should we choose Netlify then?

from website-metalsmith.

Great! Let me know when credentials are ready so I can start a PR to work on the new workflow

from website-metalsmith.

I'd need the badge to be there to do that.

from website-metalsmith.

Should we wait a reasonable time then to see if anyone has any objections with Netlify? If not, I have time to add it now

from website-metalsmith.

Open a PR, let's wait a day or two to land it.

from website-metalsmith.

No objections here.

from website-metalsmith.

@luisorbaiceta I have invited you to Netlify

from website-metalsmith.

Great! We can now trigger deploys by connecting the account to the repo, or by setting up a workflow from github actions. I'm fine with both approaches

from website-metalsmith.