SSE | Sygnal Site Engine
Community ForumSupport Us!Micro-Consulting
  • Sygnal Site Engine ( SSE )
  • The SSE Architecture
  • What's New
  • Feature Roadmap
    • Component Architecture
    • File Copy & Augmented Builds
    • SA5 Integration
  • Installation & Setup
    • Setup Github Repository
    • Setup Netlify
      • jsDelivr
    • Setup Webflow
    • Advanced Install Notes
      • Creating a Persistent Test Env
      • Add SSE to an Existing Repo
  • Usage Notes
    • Developing with SSE
    • Building & Deploying Code
    • Code Structure
    • Page Router
    • Components
      • Components Future Notes
    • Source Structure & Key Files
      • Utilities
      • Route Dispatcher
      • Infrastructure
      • Usage Notes
    • SCSS
    • Useful Library Additions
      • Adding Libraries
      • Luxon
      • Cookies
      • Core Libraries
      • Extending Capabilities
    • Best Practices
    • Unit Testing
      • Using Google Sheets as a Unit Test Data Source
      • Datetime & Timezone Tests
      • Best Practices
      • Page 1
  • Sygnal Devproxy
    • What is Devproxy?
    • Devproxy Setup
    • Cloudflare Setup
    • Webflow Site Configuration
    • Configurations
      • Controlling deployment flow
    • Future
  • Tech Stack
    • Source Code Repository
    • Visual Studio Code
    • Developer IDE
    • Dev Hosting
    • Code CDN
    • Devproxy
  • Further Development
    • Dev Team Notes
      • Engine Mode
    • Reference Project
    • Future
      • Component Development
      • Reactive State Management
      • Expand Script Loading
    • Devmode
    • CI/CD Discussions
      • Page 2
    • SA5
  • Tools
    • Webflow Designer Notation
  • SPECIAL ENHANCEMENTS
    • cookie.js
    • PostHog
Powered by GitBook
On this page
  • Why Netlify?
  • Video Tutorial
  • Setup Production CDN
  1. Installation & Setup

Setup Netlify

Setup Netlify as your site engine code CDN

PreviousSetup Github RepositoryNextjsDelivr

Last updated 9 months ago

Sygnal prefers Netlify for our SSE deployments, however there are many other CDN frameworks you can utilize;

  • Coolify

  • jsDelivr

  • NPM

Why Netlify?

  • Generous free tier. If you use a public repo, you should not need to pay anything for the SSE setup we're using here.

  • Direct integration with Github.

  • Automatic build triggers on Github commits. Simplifies the CI/CD setup, generally avoiding the need for Github Actions in a typical SSE setup.

Also,

  • Ability to deploy from private organization-owned repos if you want to, on a paid Netlify plan.

  • Lots of additional capabilities, like serverless functions. br

Video Tutorial

Setup Production CDN

Create a new site in Netlify;

Connect to your repo;

  • Click Github option

Configure your site settings;

Setting
Value
Notes

Site name

e.g. mysite

Use something unique that represents your site

Branch to deploy

main

Base directory

( blank )

Build command

npm run build

Publish directory

dist

Functions directory

( blank )

Deploy

Test it

e.g. if your site name was mysite, your code would be CDN delivered at;

https://app.netlify.com/start
https://mysite.netlify.app/index.js