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
  • Deploying to TEST
  • Deploying to PROD
  • Overview
  1. Usage Notes

Building & Deploying Code

In our simple configuration,

Deploying to TEST

Deployments to TEST are done within VSCode.

  • Save your work

  • Build your project, npm run build

  • Check in the files changed, and commit them back to the dev branch

  • Push the changes to Github origin

Wait 10 seconds for Netlify to complete the build, and your changes are live on your TEST site!

This assumes you've setup a persistent TEST environment, discussed under advanced install notes in the setup guide. This is useful primarily if you want your clients to be able to review TEST changes before you bring your changes to PROD.

Deploying to PROD

Deployments to PROD are done within Github

  • Do a PR from to merge the changes from the dev branch to main

  • Merge the PR

Wait 10 seconds for Netlify to complete the build, and your changes are live on your production site!

Overview

PreviousDeveloping with SSENextCode Structure

Last updated 10 months ago