Deploying an Angular 6 Application to Netlify
Netlify is an excellent platform for building, deploying, and managing web applications. It supports automated deployment using GitHub webhooks and also provides some advanced features such as custom domains and HTTPS all for free. Deploying a Static Site to Netlify is a breeze. Although it does support running Angular JS applications, there are a couple gotchas in the deployment process that I had to wrangle together from various blog posts in order to get things to work.
Enable Redirects
The first issue that I ran into was after I deployed my site to Netlify, whenever I would click on an Angular link, I would get a 404 page.
[caption id=“attachment_698” align=“alignnone” width=“640”]
Looks like you’ve followed a broken link or entered a URL that doesn’t exist on this site.[/caption]
Getting this to work is pretty simple. Ultimately you just need a file called _redirects in the root of your web project. In order to get angular to create this you need to do the following things. This file will send all URL’s to the root of your application which allows the Angular router to kick in and do its thing.
- Create a
_redirectsfile in thesrcdirectory of your angular project.For most basic sites it should look something like this.
# src/_redirects /* /index.html 200 - Add this file to your
angular.jsonfile.Your
angular.jsonfile serves as a configuration for many different aspects of the angular CLI. In order to get this file into the root of your output directory you must define the file here. A snippet of my file is shown below. Update this configuration file and push all of your changes back up to GitHub.{ "$schema": "./node_modules/@angular/cli/lib/config/schema.json", "version": 1, "newProjectRoot": "projects", "projects": { "flagviz": { "root": "", "sourceRoot": "src", "projectType": "application", "prefix": "app", "schematics": {}, "architect": { "build": { "builder": "@angular-devkit/build-angular:browser", "options": { "outputPath": "dist/flagviz", "index": "src/index.html", "main": "src/main.ts", "polyfills": "src/polyfills.ts", "tsConfig": "src/tsconfig.app.json", "assets": [ "src/favicon.ico", "src/assets", "src/_redirects" ... rest of file
Configure your Netlify Project
Now that you have the redirects file in place. You can set up your project for automatic deployment with GitHub and Netlify.
Once you have logged into Netlify, click on New Site From Git and find the name of your project.

Configure Build Settings
The last step is to configure your build settings.
For Build command you should enter ng build –prod.
For Publish directory you should enter dist/$NAME_OF_YOUR_PROJECT.

Be sure to replace $NAME_OF_YOUR_PROJECT with the actual name of your project.
Now you can click on Deploy site and once the initial deployment has completed you should see your new angular application running on Netflify with a working routing system.
Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.
Check out some more stuff to read down below.
Most popular posts this month
- SQLite DB Migrations with PRAGMA user_version
- Using cgit
- Lev Lazinskiy
- Making cgit Pretty
- My Custom Miniflux CSS Theme
Recent Favorite Blog Posts
This is a collection of the last 8 posts that I bookmarked.
- AI Mania Is Eviscerating Global Decision-Making from Ludicity
- No-One Escapes the Permanent Underclass from Fernando Borretti
- Is it ethical to use AI? from charity.wtf
- The logical destination of LLMs from Andy Bell
- Revised rules of engineering leadership. from Irrational Exuberance
- The circus freaks of open source from Drew DeVault's blog
- Clanker: A Word For The Machine from Armin Ronacher's Thoughts and Writings
- I ran a half-marathon! from gluecko.se
Articles from blogs I follow around the net
Safari and system design, pt. 2
Around the time I was writing about iPhone’s Safari breaking the expected “tap to jump to the top” gesture, a conversation on social media pointed to yet another thing that this tab control does strangely. A typical use of Safari means two groups of sites:...
via Unsung July 23, 2026Issue 107 – An unserious offer
The crypto industry has spent $200 million to get a bill too corrupt for Democrats to pass and a president too corrupt to sign anything that might meaningfully limit his grift.
via Citation Needed July 23, 2026It's the end of reading as we know it! It's the new Dark Ages!
If you read The Atlantic, or you follow a lot of writers on Substack — or virtually any other writing-focused website or form of social media — you will already know what this post is about: The Atlantic published a piece recently entitled The End of Readi...
via The Torment Nexus July 23, 2026Generated by openring