Surge – Static Web Publishing for Front-End Developers

Re:Surge – Static Web Publishing for Front-End Developers by bennylope on Friday June 10, 2016 @03:48PM (#11879440)

I wouldn't be too quick to say it's too expensive.

My set up is not dissimilar to your own. I'm comfortable working on the command line, using s3cmd to sync the site, modifying bucket policies, etc. Once you know those things - or if you enjoy learning them - it's all pretty trivial, but if you don't... well don't underestimate the hassle for someone who doesn't know this stuff. I'd think it a waste to pay $13/mo for what I'm happy to throw in an S3 bucket, but that's 3 venti lattes for someone not to have to deal with any of it. It's not the file storage they're charging for.

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by juandazapata on Friday June 10, 2016 @03:56PM (#11879516)

I agree with you. It's just too expensive for me, maybe not for others.

In the end they are just tools, and you should use whatever fits you better.

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by g4k on Friday June 10, 2016 @06:45PM (#11880743)

For low volume projects it is clearly too expensive.

I prefer a volume based pricing model like 5apps is offering it: https://5apps.com/deploy/plans

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by cfjedimaster on Friday June 10, 2016 @03:57PM (#11879527)

Also remember that's 13 bucks to get custom SSL, redirects, etc. If you have simple pages w/o the need of https, it costs nothing.

[ Parent | on HN ]

Re:Surge – Static Web Publishing for Front-End Developers by djsumdog on Friday June 10, 2016 @07:12PM (#11880903)

I think that SSL is just for surge.sh subdomains. I didn't see anything about lets-encrypt SSL on custom domains.

[ Parent | on HN ]