floridahackers / fh-platform Goto Github PK

Looks like SwmapHacks is missing.

http://2018.swamphacks.com/

This is issue is an umbrella to keep track of work that will be done to move the FH site to Netlify.

A bit of background.

Currently the site is hosted on a Digital Ocean (DO) droplet paid by yours truly. The original reason to have it there rather than just GH pages was to leverage DO's DNS management and to be ready to have multiple sites there if needed (i.e. the floatie.floridahackers.com) site and to be able to handle potential backend implementations and server side things.

These consideration were made before we moved most collaboration to github and leveraged PRs, repos, and slack/fb for initiatives. That also meant we had to overcome some technical limitations. Since we're on the smallest DO droplet, ram is scarce so we had to leverage Travis CI nodes to build the site, as a nice side effect we got continuous delivery whenever PRs are merged. However this is mostly overkill for a site like FH, and it's about time to address that.

On using Netlify:

Netlify has great support from the development community. It's used by React, Vue, and many others open source communities, and it has a lot of features that make it a prime target for the FH site:

• It's free. This is probably the main reason, on top of it being reliable and trusted.
• Self managed https certs. I was thinking on setting up certbot but why do that work when we could have it done for us
• GitHub integration. Netlify will build on any new changes to master, and on top of that it will also deploy PR preview deployments for PRs that are submitted. This aligns perfectly to our PR process to add events to the site, and for any other changes, since it allows for easier verification of PRs.
• Removing travis overhead. Travis is great, but it was merely a workaround, and we don't really need it.

Potential hicups:

• Right now this will be under my Netlify account, which I don't mind at all, and I'm pretty sure I can add interested collaborators as admins on Netlify to not have a single person point of failure. This is kinda the case with DO however there's there are a couple of people in the DO team.
• DNS will need to accommodate an external host, which should be fine.

Side wins:

• I can buy me coffee with the money saved on the DO droplet.

I will post updates as any issues arise, though it should be fast, and will submit a PR to remove the Travis scripts and to update any relevant docs/readmes etc.

Could be much better when it comes to selecting dates.

See in this page floridahackers.com/add-event.html

Would be great to add links to our social media places.

• Facebook Group/Page
• Twitter
• Medium
• GitHub

and the "Made with <3 by Florida Hackers" footer mark like in the Floatie site