✳flâneur — a map of the web's best reading

Why I'm using Surge and not GitHub Pages - DEV Community

dev.to · 2,166 words · saved by 1 readers

Update Will leave a small disclaimer here that Surge hasn't seen many updates to its repo recently so be aware of that. Certainly safe to use now (haven't seen any vulnerability warnings), but worth looking out for in the future. If the project ends dying off Netlify and Zeit Now are great alternatives that offer similar benefits over GitHub Pages 👍 GitHub Pages is so prolific at this point it likely needs no introduction. Surge, on the other hand, is a much lower profile project. It accomplishes the same goal as GitHub Pages, allowing one to publish their static site on an accessible URL of whatever name they choose complete with an "https." Where surge differs is in how that website gets put on the world wide web. Surge lets you get from 0 to published in the command line without any extra setup. Once you install the package, you can use their CLI in your project directory to whip up an account... enter your domain to deploy to... and boom 💥! You're up and running. Note I'm using a

Update Will leave a small disclaimer here that Surge hasn't seen many updates to its repo recently so be aware of that. Certainly safe to use now (haven't seen any vulnerability warnings), but worth looking out for in the future. If the project ends dying off Netlify and Zeit Now are great alternatives that offer similar benefits over GitHub Pages 👍 Hm, so what's a "surge" exactly? 🤔 GitHub Pages is so prolific at this point it likely needs no introduction. Surge , on the other hand, is a much lower profile project. It accomplishes the same goal as GitHub Pages, allowing one to publish their

Explore this link on the map →

saved by

related reading