- handbook
- Company
- Company
- Board
- Communications
- Decision making
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Cryptography Policy
- Data Management Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Secure Development Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Information Security Policy and Acceptable Use Policy
- strategy
- values
- Operations
- Product
- Feedback
- Metrics
- Node-RED Dashboard
- personas
- Plan
- Pricing Principles
- Product Categories
- Strategy
- Versioning
- Development & Design Practices
- Design
- Development
- contributing
- Front End
- How We Work
- Markdown How-To
- packaging
- Releases
- security
- staging
- Using Git
- Website A/B Testing
- Internal Operations
- Legal
- People Ops
- Sales & Marketing
- Marketing
- blog
- Boiler Plate Descriptions
- Content Channels
- Content Types
- HubSpot
- Marketing
- Marketing - Website
- Video
- Webinars
- sales
# Digital Ocean Release Process
When a release is tagged in the Digital Ocean repository a GitHub Action will run and rebuild the image.
Once complete the Release Manager should post to the #dev slack chanel to ask somebody with Digital Ocean access to do the following steps.
- Log into the FlowFuse team on Digital Ocean
- Navigate to the "Images" section, from the "Manage" options in the left hand menu
- Select the new image from the "Droplets" list and click on "More"
- Select the "Update Marketplace 1-Click App"
- Update the version numbers and any documentation in the Marketplace form
- Submit the new image for review, this will take 3-4 days before the new version is on the Market Place