There is no UI for adding variables (yet), so removing them shouldn't be
allowed. Removing and adding is still possible using the 'Advanced' view
by editing the YAML directly.
To make it simpler for people to work with variables, I think it's a
good idea to create some predefined ones (and not them be deleted). This
also allows us to include some indication as to the semantics of each
variable in the web setup, making it easier to work with.
Get rid of Vue.js specific getters/setters and __ob__ properties via the
JSON dumper. It is less sensitive to this than the YAML dumper (the latter
complains about some thing being `undefined` without saying what, and I
can't find it either).
When `websetup.hide_infra_settings` is true, the websetup will hide
certain settings that are infrastructure-specific. For example, it hides
MongoDB choice, port numbers, task log directory, all kind of
infra/hosting-specific things. This is used, for example, by the
automated Azure deployment to avoid messing up settings that are
specific to that particular installation.
This is necessary to run Flamenco Manager from a different directory than
the extracted tarball. Also an error opening the file is now shown in the
image, and some logging was improved.
Dynamic Pools allow you to spin up or remove virtual machines running
Flamenco Worker. Pools can be resized from the Flamenco Manager
dashboard.
The code architecture is mostly set up to support multiple platforms
(like Google Compute, Amazon Web Services, Azure Batch, etc.). Currently
only support for Microsoft Azure Batch has been implemented. To really
properly support multiple platforms some changes will have to be made,
but those are better made when there are actually multiple platforms to
support.
The pool status is polled periodically using the platform's API. The
polling period is dynamic, and depends on whether the Manager dashboard
is actually open in a browser window.
