21–30 of 33 posts
For what it's worth, you can do redirects on GitHub Pages with HTML redirects: https://help.github.com/articles/redirects-on-github-pages/
I'm with you on avoiding AWS for static sites as there are much easier options like the above.
A small static site on S3 with the free cloudflare plan in front will cost you ~$0.50 per month, with moderate traffic. Probably less than fifty cents, especially to start with, if your traffic is low. They support all the requested features. Yes, hosting this on S3, with either cloudfront or cloudflare, does take some (one time) setup. The payoff is that you don't have to rent and deal with a server and ongoing cost…
Just curious about the 301 requirement, what is your use case for this? Ie wondering if this is something we should consider supporting.
At https://www.sunsed.com we are working on a solution exactly as you described! Not ready yet! I just want to see what you think about it in your case. In version 3 (currently under development) you'll have a server.htmlpp to custom route your traffic and a file manager to treat your website content as static files. You'll be able to import/export from any static website generators. Also edit online and use a comman…
Its a hobbyests dream!
I love openshift from what Ive been using it for so far.
Earlier quoted context omitted.
GitHub Pages already have a CDN, so why add cloudflare? And as mentioned in my post, Github doesn't let you have some kind of htaccess, so no 301 redirect are possible. And I need that feature.
Cloudflare allows you to perform redirects. https://support.cloudflare.com/hc/en-us/articles/200172286-H...
Github pages supports auto-redirect between www and apex domains (redirecting from whichever you make the primary approach from the other) does that cover your 301 needs or are you needing it more broadly than that?
> 2. A CDN, for super fast loading.
> 6. oryginal content on your pages.
disclaimer: I work at Aerobatic