41–50 of 201 posts
Earlier quoted context omitted.
We use cloudflare on our Github pages custom domain, so you can easily get https support that way.
People need to stop calling Cloudflare's offering HTTPS support. It's snake oil.
The main differences on mine are:
- I use Jekyll, which is ranked #1 in the static site generator space.
- Hosted on AWS S3.
- CloudFront in front of S3.
- Routing and aliases handled by Route53.
- Deployed using a tool called s3_websites (change detection only uploading generated files AND cloud front cache invalidation for only the changed objects).
- Coded in a Docker container via a cloud IDE called c9.io using the Ruby template.
- Generator and site files committed to a GIT repository hosted on AWS CodeCommit.
Might be a little off-topic but hopefully relevant enough. I'm rather new to web dev but currently have a static website hosted on AWS S3. My current workflow is to code the HTML and CSS files using Sublime Text then upload these files into a bucket manually via the AWS console. Is there a more efficient way to do this? And is there a simple way to enable HTTPS?
Earlier quoted context omitted.
Wouldn't SSL via GitHub's cert protect that part?
Yes. It will.
Full SSL doesn't really protect you since Cloudflare won't check if the certificate is valid, an attacker could make their own self-signed cert and MITM you.
Full SSL (Strict) requires a valid cert for the domain being requested. If you had that, you wouldn't need Cloudflare in the first place.
I host mine on Digital Ocean. I commit the code to github, dev branch is deployed to stg.mydomain and master is deployed to mydomain. In terms of deployment, I use Caddy which, with ~3 lines of config will auto-TLS your site using Lets Encrypt, and handle renewing the certs for you each month. Caddy also automatically pulls your changes, builds them with hugo and deploys them with ~2 more lines of config. It's the ea…
Assuming your blog is technical, this would have been a good chance to get some more traffic by at least mentioning the actual domain, linking to the github repo, or having one or both of those in your profile. Edit: Not sure why this has been met with a stream of downvotes. Is there something wrong with saying "I use a different approach to publish this blog: [link]," especially if it's technical and would be of int…
Earlier quoted context omitted.
Assuming your blog is technical, this would have been a good chance to get some more traffic by at least mentioning the actual domain, linking to the github repo, or having one or both of those in your profile. Edit: Not sure why this has been met with a stream of downvotes. Is there something wrong with saying "I use a different approach to publish this blog: [link]," especially if it's technical and would be of int…
How do you down vote on HN?
I wrote a similar blog post: https://tberra.com/aws/amazon/meta/2016/11/12/the-birth-of-a... The main differences on mine are: - I use Jekyll, which is ranked #1 in the static site generator space. - Hosted on AWS S3. - CloudFront in front of S3. - Routing and aliases handled by Route53. - Deployed using a tool called s3_websites (change detection only uploading generated files AND cloud front cache invalidation for…
I still use Jekyll too. It's awesome. It powers my main site (about 100 posts) and builds "fast enough" where it doesn't get in the way.
Although I use DigitalOcean and use Ansible to build / deploy the site. A couple of lines of yaml lets me deploy a new site with HTTPS (using Let's Encrypt).
I built my own custom static site generator (python + jinja2) for running my side project[1]
I just git push and Netlify picks it up. Simple, to the point and no JS.
[1] I run https://discoverdev.io , a "product hunt" for top engineering blog posts!
I have access to all the npm ecosystem. Is fast. No bloatware or weird code.
Styles with styled-components for easy maintenance. https://mateom.io
Deployed to an S3 bucket connected to CloudFlare.
I just type 'yarn deploy' and it builds my blog and pushed it. And I can commit everything to source control as they keys are in aws-cli