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
Host using Github + Netlify #12
Comments
This looks like it might be better than surge due to SSL (free surge only has "basic SSL" and no http -> https 301s). I'm happy with any website hosting option as long as it does not dramatically change code to be vendor specific. |
Fixed it by changing branch to master (our building process isn't that simple ;) )... Also:
So, we should continue to build via travis and then simply host the master branch... Netlify will automatically update on each git push - so should update after each travis cron job... |
@bmpvieira - can you set up the DNS for bionode.io https://www.netlify.com/blog/2016/03/14/setting-up-your-custom-domain/ |
Now using Netlify: https://www.bionode.io/ Will add a http:// to https:// redirection once #13 is merged... |
I would suggest that we use Netlify to host the Bionode website:
Pros:
CONS:
Tutorial: https://www.netlify.com/blog/2016/09/29/a-step-by-step-guide-deploying-on-netlify/
Note - we might not even need Travis anymore to run the build command - it's possible to do this with netlify.
This is what happens when we run the website through the netlify site tester:
The text was updated successfully, but these errors were encountered: