>Free SSL for surge.sh subdomains
Wow! Thanks! It's not like I can just get it for free on any domain I like. Not even speaking about servers like Caddy that can do that automatically on launch.
Surge – Static Web Publishing for Front-End Developers
11–20 of 80 posts
Re: Surge – Static Web Publishing for Front-End Developers
#12>Free SSL for surge.sh subdomains Wow! Thanks! It's not like I can just get it for free on any domain I like. Not even speaking about servers like Caddy that can do that automatically on launch.
Why the snark? Is this how you communicate in everyday life?
Re: Surge – Static Web Publishing for Front-End Developers
#13I'm not a paying customer of or affiliated with Surge—just a happy user. Surge is what I've always wanted to when I do frontend development for fun and learning. This is especially true if you're new. When you're new, you don't want to set up a server to push to Heroku or Digital Ocean, you may not want to use GitHub pages, or other alternatives (not aware of all, just the ones I mentioned). You may still be new to g…
I'm still confused what this service does. `surge -p build` and `npm install --save-dev surge` is simpler for a newbie than getting sftp credentials to a shared host? My designer friends can drag and drop, but certainly stay away from the console.
Re: Surge – Static Web Publishing for Front-End Developers
#14Interesting idea for making kind of a PaaS for static websites.
I have been using a Firebase Hosting [1] (provides free https, CDN, CLI publish with `firebase serve`) for a while. Obviously, Firebase quotas and pricing is way another but I am curious how do you compare Surge to Firebase Hosting?
Re: Surge – Static Web Publishing for Front-End Developers
#15See also https://www.netlify.com/ ... Not sure on exact differences between the two, maybe someone who's used one or the other can chime in?
Re: Surge – Static Web Publishing for Front-End Developers
#16If you're interested in setting up something similar on AWS, you could take a look at Stout [1].
[1] http://stout.is
Re: Surge – Static Web Publishing for Front-End Developers
#17Nice service, but too expensive to be honest. My static websites (built with middleman) are hosted in Amazon S3 as a static website bucket and have a Cloudfront distribution in front of it. I use `middleman s3_sync` to deploy the build in one command and it takes care of everything, even Cloudfront invalidation. All for just a few pennies per month. Anyway, keep up the good work.
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.
Re: Surge – Static Web Publishing for Front-End Developers
#18I mean, if you're doing a static site you can also use github pages with a simple push command. Is there some difference between surge and doing this that I'm not seeing?
Re: Surge – Static Web Publishing for Front-End Developers
#19I'm not a paying customer of or affiliated with Surge—just a happy user. Surge is what I've always wanted to when I do frontend development for fun and learning. This is especially true if you're new. When you're new, you don't want to set up a server to push to Heroku or Digital Ocean, you may not want to use GitHub pages, or other alternatives (not aware of all, just the ones I mentioned). You may still be new to g…
I'm still confused what this service does. `surge -p build` and `npm install --save-dev surge` is simpler for a newbie than getting sftp credentials to a shared host? My designer friends can drag and drop, but certainly stay away from the console.
You'll need a shared host first. surge automatically gives you that.
Re: Surge – Static Web Publishing for Front-End Developers
#20If you're interested in setting up something similar on AWS, you could take a look at Stout [1]. [1] http://stout.is
+1 -- I use Stout all the time. I don't have to rely on anyone's uptime except AWS's. Stout's just a "shortcut" for using AWS infrastructure that I have full control of.
With Surge, I'd have to trust some startup's build tool not to fail at a vital time.