- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Data Management Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- strategy
- values
- Operations
- Product
- Feedback
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Product Categories
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Boiler Plate Descriptions
- Marketing - Website
- Customer Stories
- Webinars
- Social Media
- blog
- Sales
- Engineering & Design Practices
- Design
- Engineering
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Project Management
- Releases
- Security Policy
- tools
- Internal Operations
- People Ops
# Platform Ops
# CI/CD
As part of our CI/CD pipeline in our @flowfuse/flowfuse repository, we perform the following actions when code is merged to the main branch:
- Several backend and UI tests are executed against the code by this pipeline
- Once all tests complete with success, FlowFuse npm package is built and published to the npm registry with a
nightlytag by this pipeline. - FlowFuse npm package is built and published to the npm registry with a
nightlytag by this pipeline. - The same pipeline triggers another action, responsible for building a container image
- Container image build pipeline uses flowfuse npm package created in step 1 (tagged as
nightly) to build a fresh container image - The resulting image is used to perform deployment on both staging and production environments.
You can read more about our various environments here:
- Pre Staging - used for each individual pull request as part of the code review process.
- Staging - triggered by merge to
mainbranch, used for testing the full application, without fear of damaging the production environment. - Production - the live environment that our customers use.