• Allow installation of multiple applications using the same image on the same instance (exclude presearch)
• Check for applications availability is adjusted
  • previous scheme was testing availability of installed applications. That had some limitations as ports may have been in use by the application and so respond in a different than expected way. Furthermore the test was only done on nodes on which some application was running
  • FluxOS will now choose a random unused port within application range and test availability of that port by running a simple listening server. This test is way more deterministic, predictable and properly tests even nodes without any app running.
• FluxOS Home Dashbord adjusted for halving with taking data about rewards directly from daemon.
• Introducing Flux Storage on Home UI
  • Storage for big variables and other parameters: https://github.com/RunOnFlux/fluxstorage
  • Upload Envionment parameters, Commands or Contacts to central Flux Storage managed by Flux team.
  • This allows for long list of Environment parameters or commands going beyond FluxOS character limitation.
  • Furthermore Environment parameters and Commands provide slight obfuscation as they are not directly stored on FluxOS but only as a link to Flux Storage that only FluxOS itself can access. This should definitely not be treated as private storage but just as a slight obfuscation mechanism
  • Contacts on the other hand if used in Flux Storage are fully private. Only Flux team managing Flux Storage can access it. This provides a set of anonymity where you email won't be exposed publicly. Contacts field is used primarily for notifications about applications - expiration, launches and more.
  • Flux Storage can be directly used on Home UI in app registration or update.
  • The Flux backend scheme for Flux Storage is F_S_[CMD, ENV, CONTACTS]=URL
• Introducing Apps Monitor https://github.com/RunOnFlux/appsmonitor
  • Very basic tool on which we will expand to add functionality of application monitoring, notification system via email and other provided contacts
• As Flux grows we are forced to protect development team, node operators and users of Flux by applying Terms of Service. This forces more strict rules on what can Run on Flux. https://cdn.runonflux.io/Flux_Terms_of_Service.pdf
• Don't allow incoming connections from non-routable ips