FlowFuse / FlowFuse/helm

Consider building Flowfuse container image as a part of `FlowFuse/flowfuse`

Open
#428 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go Template
Stars
5
Forks
17
Avg merge
3d 2h
Merged PRs (30d)
21

Description

This task aims to collect opinions about the idea. Prpper tasks should be created once decision is made.

---
At this moment the flow for building flowfuse app used by the FFC is:

1. Update the code within `FlowFuse/flowfuse` repo
2. Build the npm package (`nightly`)
3. Trigger container build in `FlowFuse/helm` repo
4. Update container image and trigger FFC deployment workflow in `FlowFuse/CloudProject`

Running container image build as a part of `FlowFuse/flowfuse` will:
* shorten the delivery time
* simplifies FFC deployment tracking
* decrease the management burden

Also, keeping contianer image build next to the application code is a common approach.

Same approach could be made to fileServer container image.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.