Static Site Generators have become increasingly popular over the past several years. They’re great for any projects not requiring server-side processing. There’s been an emergence of services such as webtask.io and others for handling server endpoints. This has no doubt contributed to the growth of static sites and “serverless” web applications. Many see this as a major new direction for web app development. One such tool for dealing with static sites is Surge.
Of the many draws for using static site generators, the relative ease of building and deploying is significant. These types of deployments simplify the oft-involved and tedious process of setting up and managing a production server. This blog post will give an introduction to using Surge. It is an easy-to-use tool for deploying a production-ready static sites in a matter of minutes.
What is Surge?
Installing Surge and setting up an account is extremely simple. Open up a new terminal window and type the following command:
npm install --global surge
(Note: this step assumes Node and npm are already installed on your system. If not, you can install the latest version of both from the official Node.js website.)
Upon your first time setting up, Surge will ask you to set up an account. The only requirements are is providing an email address and password, and verifying your email afterwards. Upon completing this step, you’ll now be setup with a Surge account and ready to deploy to their service.
Deploying your site
To deploy your static site to Surge, first find the file path of the project directory you want to deploy. As an example, I’m going to deploy a project located at
Once you know the file path of the directory to deploy, run the following command in a terminal window:
Your username (i.e. email address) will then display. Afterwards, you’ll just need to provide the file path for the project:
Enter the full file path, then hit enter.
Surge will automatically provide a domain name using random words. You can also create any custom domain if it is not already taken. Enter your chosen domain name, then hit enter.
(Note: If the custom domain name you input is already taken, you’ll see an error message.
Aborted - you do not have permission to publish to [<custom-domain.surge.sh>]
Once deployment is complete, you’ll see a success message displayed in your terminal. The domain name and IP address for the project will show you where you can access the live deployment.
Enter the domain name into your web browser and you should now see your site live:
Adding a custom domain name for your site
By default, Surge will provide a custom subdomain for any site that you deploy to their service. It will look something like
your-custom-domain.surge.sh. You can customize and select what the subdomain is (provided it’s not already taken). Chances are, though, that you’ll want to use your own custom domain for any professional project.
To do so, you’ll want to add two new
CNAME records in the DNS panel of your domain provider. One will be with a hostname of
@, and the other will be with a hostname of
CNAME records will point to the following IP address:
If for some reason your domain provider doesn’t allow
CNAME records, you can set an
A record as an alternative. Have the
A record point to an IP address of
Using custom subdomains
You can also use any custom subdomain to point to Surge, such as
sub.my-cool-site.com. To do so, you’ll want to set up a new
CNAME record. This should point to the same
na-west1.surge.sh IP address above, but this time the hostname will be
* hostname is a wildcard. This means that any subdomain apart of the primary domain will be valid and allowed.
Surge will recognize these DNS changes immediately. It can take take time to propagate elsewhere, however, typically no more than 24 – 48 hours.
Deploying your project using a custom domain
Once the DNS settings have taken effect, you can now deploy your project. You’ll just need to indicate the domain that you’d like to use. To do so, run the
surge command in your terminal. Indicate the file path to your project first, then the custom domain afterwards, like so:
surge filepath/of/project a-cool-custom-domain.com
Bind your custom domain to the project
You may want to bind your domain to the project so you don’t have to enter it whenever you deploy. You can do so using the
echo command, directing it to a
CNAME file, like so:
echo a-cool-custom-domain.com > CNAME
Much like the
.gitignore file in the Git ecosystem, Surge offers its own ignore file. You can set up a list of files and directories that Surge will ignore at the time of deployment. This is useful for leaving out files that may only be relevant during the development process. Anything that you might want to keep entirely private is good to include here as well.
To set this up, create a new file called
.surgeignore in the root of your project folder. Inside of this file, you can list any files and directories you’d like to to ignore. Some common examples might include
bower_components, and others. You can also ignore specific file types that aren’t relevant to the production version of a site. Adding
* (the wildcard symbol) before the extension (i.e.
*.psd, etc.) will accomplish this.
Take down your site from Surge
If for some reason you’d like to take down your site, you can do this easily with the
surge teardown command.
surge teardown your-domain.com
- LA County WIC Data
- Laycut Records
- Lolli Couture
- Madd Music Management
- Mark Petrie
- Musicians Booking
- Ocean Aid Hawaii
- Omega Water
- Permit Advisors
- Quick Uniforms
- Remote Web Guard
- Right Choice Developments
- Sakura Sushi Bar
- San Fran Ortho
- Sauk Valley Tennis
- Shark Tech
- Size Xchange
- An Introduction to Version Control using Git (2018 Update)
- Bash vs Zsh: A comparison of two command line shells (2018 Update)
- Did you just launch a new website? The ultimate guide on what to do next.
- Some common use cases of Sass
- WordPress Designer
- An introduction to the htaccess file:The Ultimate Guide (2018 Update)
- Build or Buy – Determining the Right Software Solutions for Your Business
- How to get rid of the “You have mail” Unix message
- Using node-sass to compile Sass files in an npm script
- Advanced Features of ECMAScript 6: The Ultimate Guide 2018
- Our custom design process
- Designing a simple navigation bar with Bootstrap 4
- Software Development Services
- Using A CSS Reset For Better Cross-Browser Compatibility
- Using WOW.js and Animate.css for Scroll-Triggered Animations
- WP Engine’s Staging Area has Revolutionized Our WordPress Development Process
- Responsive Web Design
- Medical Web Design
- Web Video Production
- Los Angeles Web Designer
- Tips For Keeping Your WordPress Site Secure
- Using chunkwm as a window manager
- Refactoring CSS Code (2018 Update)
- Using TextExpander To Increase Your Productivity
- Using ImageOptim for reducing image file sizes
- 4 Ways To Keep Your Data More Secure
- WordPress FAQ