Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Netlify instead of Github Pages #89

Closed
geekyme opened this issue Aug 27, 2020 · 2 comments
Closed

Using Netlify instead of Github Pages #89

geekyme opened this issue Aug 27, 2020 · 2 comments
Labels

Comments

@geekyme
Copy link
Collaborator

geekyme commented Aug 27, 2020

Advantages:

  • Simplify deployment. No more docs/ folder in version control. Just push new code to repo, and a github webhook will hit netlify to pull the source code for deployment.

  • Potentially better savings on page speed

  • Access to Netlify CDN & Netlify CMS

  • Free, with SSL too.

Disadvantages:

  • More lock in to a vendor
  • Netlify CI can only build static site. So if we want to do more stuff like running tests, those will still go into github workflow.

Some references:

@geekyme geekyme added the enhancement New feature or request label Aug 27, 2020
@erickhun
Copy link
Collaborator

erickhun commented Sep 4, 2020

@geekyme , I kinda prefer to keep everything in a single place if possible , so it keep things simple for now.
I like our current because everything is in github. The more tools we use, the messier/more complicated it could get.

@geekyme
Copy link
Collaborator Author

geekyme commented Sep 4, 2020

Make sense. 👍🏻 I'll close this for now as an idea in the future if we need it.

@geekyme geekyme closed this as completed Sep 4, 2020
@geekyme geekyme added idea and removed enhancement New feature or request labels Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants