Deploy Previews using Netlify

[maxrjones]

As noted in https://guide.cloudnativegeo.org/contributing.html#contribution-workflow, the contributor process of fork -> staging -> main is non-ideal, mostly because it is clunky for contributors and reviewers.

One solution would be to apply for a Netlify open source account for the Cloud Native Geo project and configure a Quarto deploy for Netlify. This would make the security concerns from rossjrw/pr-preview-action#6 irrelevant because the deployment would not commit any code to the repository.

curious for thoughts from @zacdezgeo @wildintellect @jsignell @abarciauskas-bgse

[zacdezgeo]

I'm in a favour! So, in terms of workflow:

• forks would go target main
• once merged, Netlify deploys it from some of their own process (It's unclear to me how this happens)

[maxrjones]

once merged, Netlify deploys it from some of their own process (It's unclear to me how this happens)

This is accurate, however Netlify can also deploy previews from PRs off forks. Here's an example of what this would look like in practice - pangeo-data/pangeo.io#102 (comment).

One additional component to be aware of is that we'd need a domain administrator to allow us to configure the DNS for Netlify + guide.cloudnativegeo.org. https://docs.netlify.com/domains/configure-domains/bring-a-domain-to-netlify/#step-2-update-your-dns-configuration

[abarciauskas-bgse]

Sounds good to me, thanks for suggesting this @maxrjones. Is the next step to discuss the netlify open source account with the CNG team?

[maxrjones]

Is the next step to discuss the netlify open source account with the CNG team?

Yep! @PowerChell, @LouisaDiggs, and @jedsundwall would you support the idea of a Netlify Open Source account for CNG? If so, what's your preferred process for applying and managing access for CNG guide developers?

[jedsundwall]

I'm afraid we know nothing about using Netlify ourselves, but I've applied for an open source account. I've created a Google group to manage an email list for guide@cloudnativegeo.org – I'll defer to you on who should be added to that group and who should have access to the Netlify account. As you know, we've been pretty hands off with the administration of the guide. :)

[wildintellect]

@zacdezgeo can you make a list of who we should have admin the Netlify account?

[zacdezgeo]

@jedsundwall, @maxrjones, @wildintellect, @zacdezgeo. Open to other suggestions!

[wildintellect]

That list is good to start. @jedsundwall can you add those people to the Netlify?

[jedsundwall]

OK, I just looked into this and each user currently costs us $19 per month because they haven't responded to our request for an open source account. Can I add just one of you to have you deploy it initially and include a link to Netlify in the footer? Once we get that done, we can apply for an open source account again and hopefully add everyone else for free.

[wildintellect]

@jedsundwall , @maxrjones volunteered

[jedsundwall]

Added Max!

[maxrjones]

#166 adds previews with netlify. That should be sufficient for eliminating the need for the staging branch, meaning that the current workflow would remain for deployments from the main branch.