Earlier quoted context omitted.
Any time I hear 'Heroku' it's mentally followed by that 'it's going to be expensive' intake of air sound. Is that prejudgement borne out in reality?
$7 a month for the hobby plan doesn't seem that terrible. But, serving static assets from Ruby seems heavy handed. You also end up writing code for things other environments would handle with configuration...like redirects, cache headers, and so forth. Also, while $7 isn't a lot, it is a little more than other solutions in this hobby level space. The suggestions for Netlify and Firebase seem better ideas for static c…
Use App Engine and Go to Host a Static Website with Same Domain Redirects
21–26 of 26 posts
Re: Use App Engine and Go to Host a Static Website with Same Domain Redirects
#22Earlier quoted context omitted.
$7 a month for the hobby plan doesn't seem that terrible. But, serving static assets from Ruby seems heavy handed. You also end up writing code for things other environments would handle with configuration...like redirects, cache headers, and so forth. Also, while $7 isn't a lot, it is a little more than other solutions in this hobby level space. The suggestions for Netlify and Firebase seem better ideas for static c…
You can use Go with Heroku, with a buildpack [1]. There's a free plan, but it doesn't include SSL. [1] https://github.com/heroku/heroku-buildpack-go
Just seems a poor option compared to other choices, at least for static content.
Re: Use App Engine and Go to Host a Static Website with Same Domain Redirects
#23https://cloud.google.com/compute/docs/load-balancing/http/us...
Re: Use App Engine and Go to Host a Static Website with Same Domain Redirects
#24Earlier quoted context omitted.
app engine static files are dispatched by google cdn network for free. CloudFront is not free.
I think the OP is subverting the CDN functionality since the static assets are flowing through the golang code.
Re: Use App Engine and Go to Host a Static Website with Same Domain Redirects
#25Earlier quoted context omitted.
I think the OP is subverting the CDN functionality since the static assets are flowing through the golang code.
not flowing through, it is redirecting. The static files are really served by google cdn.
http.ServeFile(w, r, "static/"+r.URL.Path)