Configuration pinexq.toml
The pinexq.toml file is used to configure your Pinexq project.
The minimal configuration is:
[project]name = "my-project"pinexq_endpoint = "jobs.api.dev.pinexq.net"entrypoint = "main.py"
[deployment]cpu = "1"memory = "4Gi"disk = "10Gi"max_replicas = 4Extended configuration example:
[project]name = "my-project"pinexq_endpoint = "jobs.api.dev.pinexq.net"entrypoint = "main.py"
[deployment]cpu = "1"memory = "4Gi"disk = "10Gi"max_replicas = 4
[function.hello_world]deployment = { cpu = "4", memory = "16Gi", disk = "50Gi", max_replicas = 1 }defaults = { greeting = "Hello PineXQ", interval = 60 }Reference:
Section titled “Reference:”[project]
Section titled “[project]”name: The project’s identifier/name. Used to label the project in tooling and platform UI/metadata. Not relevant for the deployment.pinexq_endpoint: The PinexQ API endpoint (host/address) the project should connect to for job-related operations.entrypoint: The startup file that contains the__main__function and should be executed when running the ProCon.
[deployment]
Section titled “[deployment]”The resources each worker reserves, stated by all three of cpu, memory and disk, or by the deprecated resource_preset, not both.
Without either, the Medium preset is used. See Resources for how a worker uses them.
cpu: The CPU as a Kubernetes quantity in cores, e.g."500m","1.5"or"2". Must be a whole number of millicores.memory: The memory as a Kubernetes quantity, e.g."512Mi"or"16Gi". Must be a whole number of MiB.disk: The disk for the worker’s local files as a Kubernetes quantity, e.g."10Gi". Must be a whole number of GiB.resource_preset(deprecated, will be removed in a future release): A named sizing preset (XSmall,Small,Medium,Large,XLarge,XXLarge) that stands for fixed resources. See Resource presets for the values; usecpu,memoryanddiskinstead.max_replicas: The maximum number of replicas/instances the deployment may scale out to. Higher values allow more parallelism and throughput but increase resource usage and cost.
[function.<function_name>]
Section titled “[function.<function_name>]”Function-specific configuration that overrides the project-level configuration.
deployment(optional): replaces the project-level[deployment]as a whole for this function.cpu,memoryanddisk, or the deprecatedresource_preset: The resources for the function, as in[deployment].max_replicas: The maximum number of replicas/instances the function may scale out to.
defaults: Default function values that should be configured for the function.
TOML tips:
Section titled “TOML tips:”- TOML files do not have a
Nonevalue; instead, createdefaultsand omit those values, e.g.defaults={} - If an inline table becomes too large, it may be necessary to use a normal table. For example:
[project]name = "my-project"pinexq_endpoint = "jobs.api.dev.pinexq.net"entrypoint = "main.py"
[deployment]cpu = "1"memory = "4Gi"disk = "10Gi"max_replicas = 4
[function.hello_world.defaults]greeting = "Hello PineXQ"interval = 60encoding = "utf8"