× press ESC to close

Netlify builds, deploys, and hosts your front end.

Netlify is quite similar to PubStorm, but there are some things that are different.


On PubStorm, you had one or more Projects; on Netlify you’ll have one or more Sites. To use PubStorm, you worked completely from the command line, and you can do the same on Netlify - but some things are configurable most easily in our UI though you can also use our API. Your account is tied to your email address, and an account may own any number of sites.

This blog post provides a quickstart guide to Netlify for former PubStorm users, and you should read it before reading the below details.


The default domain for Netlify sites is sitename.netlify.com instead of sitename.pubstorm.site. In case there was already a Netlify site with your site’s name, we have prepended pubstorm- to the sitename: pubstorm-sitename.netlify.com. You can edit your sitename via the CLI or on your Site’s settings page.

You will need to update your DNS if you use a custom domain, and you need to update your bookmarks even if not.

You may only have one custom domain per free site. We recommend you configure www.sitename as the official name, and we will also serve sitename. If you instead configure sitename, we will instead automatically serve www.sitename as well. Additional hostnames for a single site are a paid feature.

You cannot remove the sitename.netlify.com “default” hostname on Netlify, as you could on PubStorm.


Any SSL certificates you had in place at PubStorm could not be migrated. However, we automatically provide one for your site as https://sitename.netlify.com.

In case you have a custom domain and have changed your DNS so it points to Netlify, you can enable SSL on the https tab of your Site settings for free. Due to caching in the Domain Name System, it may be some hours after you make the change, before this will work. Please do not try multiple times to enable SSL in case it doesn’t work the first time for your custom domain, as this may lock you out of being able to get a free SSL certificate via our system for a week!

Site passwords

If you had a site login and password set, we will automatically password protect your site with the same password (but no username is required). You can disable this or change the password via the CLI or in the settings for your Site in our UI.


While variables set in and accessed via jsenv.js will continue to work, you can no longer set them via CLI or UI - you will have to change them manually in your jsenv.js file and redeploy your site. Our Build Environment settings (shown on your Site settings page) are only exposed to your code during Site building - the deployed site will not be able to use those Build Variables in the same way you use variables in jsenv.js.

On Netlify, history pushstate is controlled differently than it was on PubStorm. The 200.html file is no longer used, so you will instead need to configure your site to work with history pushstate. Once you add an _redirects file, you will need to redeploy your site for us to start using it.

We do not generate a sitemap.xml for you. If you don’t update your site content, your existing sitemap.xml will continue to work. If you do update your content, you can make a new sitemap.xml with services like https://www.xml-sitemaps.com/


Only Site/Project owners will be able to claim sites. We will not be able to preserve the collaborators for your site during migration, so you will need to invite them to collaborate again.

On Netlify, collaborators need not be signed up for our service before you invite them to join your site (via the UI in the “Access” tab) - you can invite anyone by email address with no previous setup on their part.

Continuous Deployment

If you had your site deployed automatically when you pushed a commit to Github, you should read this!

Repository handling is different on Netlify. If you wish to automatically deploy your site to Netlify on GitHub pushes, there are some things to keep in mind:

  1. You’ll need to integrate your repository with our site. If you select “Link” from the “Link to Git” section of your Site settings, we’ll automatically connect our service to your repository after you authenticate with your Git provider. We support GitHub, GitLab, and BitBucket. At this point you can, but do not need to, remove the PubStorm webhook from your repository’s settings as we won’t use it. In case you want to disconnect our service later, we have added a Deploy Key and a Webhook.
  2. If you create a new site and link a GitHub repository during site creation, we set this up for you automatically for a site.
  3. We can just deploy your files as-is, directly from GitHub, but we can also build your site for you! If you do not set a Build Command for your site, we will just deploy your files as-is.
  4. You should specify a Public Directory in your site settings only if your site is built in some directory other than the root of your repository, eg a site/ or build/ subdirectory.
  5. Our continuous deployment functionality is rather more advanced than PubStorm’s, and is available at all account levels. For more information, please read our documentation on Continuous Deployment and Webhooks.

Notice something is incorrect or outdated?

First off, great eye! We appreciate your discovery and want to ensure it gets addressed immediately. Please let us know here.

Want to get started quick?