Releases: RunOnFlux/flux
Releases · RunOnFlux/flux
v4.17.0
- Fix app updates/renews that were below version 5.
v4.16.1
v4.16.0
- It is now possible to define specific folders from your container to be synced by syncthing. ex: '/root|s:/root/test' this will create the root container but only the test folder will be synced across the nodes running the app on the network
- Marketplace now works with Environment parameters that are stored Flux Storage
- Config reload and adjusting FluxOS configuration file no longer restarts FluxOS
- Added restart FluxOS option to Flux Admin Page
- Other improvements and fixes on Home UI
- Improvements on messages processing. Duplicated messages are no longer processed (reduces cpu and disk usage)
- Better detection of external IP address changed and broadcasts to the network
- Other minor improvements
v4.15.0
- Nodes under UPNP where router is always failing to map ports (not possible to run any app) will get DOS state on fluxOS and start failing benchmarks
- All applications are now updated to version 7 on update specifications/renew
- Improvements on Application Management Page (Tabs: Information, Resources, File Changes, Processes, Logs, Execute Commands Output - commands are now a string not an array)
- Added to Flux Admin Page the ability to adjust apiport, routerIp, blockedPorts and blockedRepositories
- Prevents nodes from installing application that is IP scoped
- Other small improvements
This version will be enforced on November 7th.
v4.14.1
v4.14.0
- FluxOS now accepts a new property on configuration file blockedRepositories.
- Node operator can define up to 10 images (organisations) that they do not want to run on their fluxNode. Repositories from Flux Marketplace can not be blocked. More information bellow
- An array of Strings ex: ... blockedRepositories: ['test/banthis', 'block/dontrunonme'] ...
- Changing configuration file automatically restarts FluxOS.
- It can take up to an hour for an application running on a node to be removed by blockedRepositories configuration changes.
- Upnp port testing adjustments
- Improvements on application update internal process
- Following API calls added:
- GET /flux/routerip
- GET /flux/blockedports
- GET /flux/apiport
- GET flux/blockedrepositories
- GET /flux/marketplaceurl
- GET /flux/adjustrouterip/:routerip? (admin privileges)
- POST /flux/adjustblockedports (admin privileges)
- GET /flux/adjustapiport/:apiport? (admin privileges)
- POST /flux/adjustblockedrepositories (admin privileges)
- Error of 'Applications port range is not reachable from outside' is now considered only after more then 100 failed attempts
- Masternode category on marketplace
- Several Updates on HomeUI
v4.13.0
- FluxOS now officially supports following distributions, Node and Mongo versions with others likely to work:
- Ubuntu 18.04, 20.04, 22.04
- NodeJS 16, 18, 20
- MongoDB 4.4, 5.0, 6.0, 7.0
- Small changes on development marketplace
- Adds port 53 to the banned port list by FluxOS as it is used by Ubuntu/Debian DNS. We are working on resolving the issues and make it available soon again
- Adds a range of ports not available on UPNP nodes to prevent the FluxOS error "Failed: Error on FluxOs response - Applications port range is not reachable from outside!"
- Other code improvements
v4.12.0
v4.11.0
v4.10.0
- Marketplace now supports v7 application specifications
- New Flux Message: 'fluxappremoved'
- This internal message is boradcasted to the Flux network whenever an application is removed from a node
- This will improve accuracy of application locations
- Improves testing of UPNP support.
- Test is conducted on Api Port + 3 with Flux_UPNP_Mapping_Test to not intervene with FluxOS ports in use
- Firewall port adjustments are now only conducted if firewall is active
- Adds language preselection to script handlings on port adjustments
- Additional precautions of handling firewall ports adjustments
- Improvements to 'fluxipchanged' messages
- Corrections in a few api paths on Syncthing Service