disk_sizeoptions can be used (only in the licensed version) to specify what kind of machines to deploy when dynamically scaling.
[env]declaration. For example:
RUST_LOGhere specifically, because this is currently controlled by the Hadean Global Logger.
RUST_LOGwill be set to
1in your applications environment variables automatically. Otherwise
RUST_LOGwill be set to
--debugargument will override these settings in this configuration file, but all other environment variables will be passed as normal.
requirementssection states what your application needs for it to be launched. In the freemium version, this also controls what resources are needed by each application that is created via the
spawnAPI. However, the full API is capable of using
spawnwith arbitrary resource requirements.
toolssection of the configuration controls what features are enabled on the platform. These features are not available in the freemium version of the platform.
clustersection of the configuration controls how the cluster scales:
standby_machinescontrols how many machines are provisioned ahead of time for scaling events.
machine_timeoutcontrols how long the system should stay idle running no application before it starts removing standby machines.
standby_machinesat 1 or above, which will ensure that you don't have to wait to scale up or down every time you use the
runcommand. If your application needs to scale rapidly, you should set
standby_machinesto at least 2, so that the platform begins creating a new VM once all VMs are in use.
source. An outbound rule is specified with the fields
[[outbound-rules]]blocks can occur in the same configuration file, where each time it appears you are specifying one additional rule. In your cloud provider, each rule may be represented as multiple rules, when using comma separated lists for ports.
--locationargument has the aliases
--region, but all of these can be used to specify which AWS region you want to deploy into:
--availability-zoneargument, along with region.
--domain-nameargument must be the exact name of a hosted zone in AWS Route53. The deployment will then automatically register a Route53 record set as a subdomain of the hosted zone with the cluster name and key. For example:
simula-123456.mycompanyname.com, depending on the key that the cluster gets when it is created. Once created, we then use Let's Encrypt to obtain a certificate for the subdomain. Note that this means that clusters created within this domain are subject to Let's Encrypt's rate limits, the most important of which is no more than 50 registrations per registered domain per week.
--locationargument to pass a location from the list below.:
hadean configcommand. Simply specify
--debugflag on any command. Analytics are on by default.