Fleio version 2021.02.0 is now available in beta and you can test it in your lab environment, since this release is not recommended for production.

You can read more about our release model here.

New fleio commands

In the latest development cycle we have added some quality of life improvements to Fleio (when installed with docker), such as:

  • Bash completion for fleio command
  • Fleio sync command
  • Fleio edit script command

With these improvements we hope to make Fleio more user friendly.

Before this release, you would have to access the utils container using fleio utils command, then change the directory to /var/webapps/fleio/scripts/ and then you would be able to run the sync script. Now you can just run the fleio sync command, as you would run any other fleio related command (status, restart, updates and so on).

Besides the fleio sync command, we also implemented an fleio edit command which will let you chose you preferred text editor and then would open the selected configuration file. With fleio edit command you can edit the following configuration file:

  • settings.py
  • enduser.config.json
  • staff.config.json
  • site_constants.js
  • staff_constants.js

Url uploads in memory streams

As we mentioned in the 2021.01 release blog post, we did some changes on how the files were uploaded in Fleio.

In the latest release, we also changed how the images uploads are handled, when the image source was an URL.

Before 2021.02 release, the image was being downloaded as a temporary file on the Fleio server, and then it was uploaded in Openstack.

This could be the target of DoS attack, so we changed it to no longer download the image on the Fleio server, but instead, to send it directly to Openstack.

Performance improvements

With 2021.02.0 release we have also made some changes to how Fleio computes client’s credit on resource create. This should result in a big performance boost

Prior to this change, Fleio would compute all the client’s data on each cloud resource create (instance, volume, network, etc) with all pricing rules, to see if the client does have enough credit at that given point.

If he has enough credit, the instance is deployed. If not, he receives a warning that he does not have enough credit even though he has positive credit (basically on next process clients cron he would get into negative credit).

We have now implemented a new settings.py feature that will allow you to enable/disable the credit check on cloud resource deploy:


This new feature is enabled by default.

Besides this new features, we also have added caching on some pricing related data, so we can reduce the mysql queries.

We’ll talk about some of the other features in the stable release, 2021.02.1, which should be out in about one week.

In the meanwhile, see a complete list of changes in the https://fleio.com/docs/changelog/v2021.02.0.html.