Documentation
Getting Started
Documentation Index Installation Details Quickstart
Architecture
Alert Geometry Coverage Data Flow Sequences Design Standards Display System Architecture Eas Decoding Summary Eas Monitor V3 Architecture Sdr Service Architecture System Architecture Theory Of Operation
Development
Agents Certification Reliability Plan Component Library Contributing Javascript Api Sdr Frequency Validation User Interface Guide
Hardware
Alpha Led Guide Argon40 Zigbee Setup Gpio Guide Gps Hat Setup Neopixel Led Control Sdr Setup Serial To Ethernet Adapters Vfd Display Setup Waveshare Rs232 Wifi Setup
Guides
Analytics And Reporting Api Key Management Audio Monitoring Audit Log Review Database Backups Disk Space Cleanup Eas Config Tool Eas Test Signal Pipeline Hardware Quickstart Help Https Setup Icecast Streaming Setup Ipaws Feed Integration Local Mail Server Manual Eas Events Mfa Totp Setup Notifications One Button Upgrade Setup Instructions Smart Setup Ssl Web Ui Guide Tailscale Setup Tts Normalization
Troubleshooting
Firewall Requirements Polling Not Working Sdr Master Troubleshooting Guide Troubleshooting 504 Timeout Tts Troubleshooting Update Not Pulling Changes
Security
Security
Reference
About Changelog Diagrams Ecig Cap To Eas Implementation Guide V1 0 Nws Alert Parameters Ohio Eas Documentation Overview Repository Statistics Vtec Event Linking
Policies
Privacy Policy Sms Messaging Terms Of Use

The GitHub Actions workflow at .github/workflows/build.yml builds and publishes a fresh kr8mer/eas-station:latest image whenever commits reach the main branch. You can treat the passing run as the guardrail that unlocks a one-button upgrade experience for operators who maintain on-premises stations.

1. Make sure the pipeline stays green

  1. Confirm the CI status badge at the top of the README is green before promoting a change.
  2. If the workflow fails, inspect the run logs for container build issues, dependency errors, Hub authentication problems and fix them before shipping an upgrade.

workers. A single command can refresh the containers to the newest image that Actions just pushed:

Wrap those commands in a shell script or a systemd service unit so field operators can execute it with a single click, a kiosk after the upgrade so operators can confirm the version change.

3. Gate upgrades on a passing workflow run

Pair the upgrade button with the status badge link. Before allowing an operator to execute the upgrade script, check the latest workflow run using the GitHub REST API or the badge URL:

  • Green badge → latest image built successfully and is safe to pull.
  • Red badge → block the upgrade and direct the operator to contact the development team.

4. Optional: Publish versioned tags for rollback

The workflow currently ships only the latest tag. If you want the button to support rollbacks, extend the

TARGET_TAG=${1:-latest}
  --build app poller ipaws-poller

Exposing the tag as a parameter lets operators downgrade to the previous known-good build in one step while keeping the default experience to pull the latest image.

Back to Documentation Index

This document is served from docs/guides/one_button_upgrade.md in the EAS Station installation.