The following complications I’d was unanticipated: GitHub had been intentionally 302 redirecting strikes straight to my personal site. This blog post sums it up nicely; in short, as a means to better mitigate DDoS attacks against their IPs, GitHub first filters against bot user agents before 302 -ing plain ola€™ humans to Pages. This can be best true for content making use of A DNS records to point personalized domain names directly at their particular machine IPs.
I really could used an ALIAS record (pluses and minuses which are well demonstrated by my DNS supplier, DNSimple) directed at jazzcrazed.github.io to handle the redirect issue, nevertheless the basic repository-cleanliness complications had me personally turned-off to content, anyhow. They tasted somewhat sour to possess my hosting condition influence my material management and resource controls in such specific approaches.
Input S3
For a number of rapid projects within my newest tasks, we put up frontend-only solutions on all of our Amazon S3 buckets. They certainly were low priced, smooth, and performant. It really seemed near a perfect match to my personal desires for this blog.
I’d way back when establish an AWS account that were idling using aim of using it a lot more straight. Now that services have myself making use of AWS very frequently, we noticed perfectly comfortable with relocating to it. Читать далее “DNS problem. For a number of quick projects at my most recent task”