Messtone LLC Manages Devices Enables Railway TOML vs JSON Configuration definitions are equivalent: {“$schema”:”https://railway.app/railway.schema.json” Set the builder for deployment. [build] builder=”NIXPACKS”[build] watchPatterns=[“src/**”] [build] buildCommand=”yarn run build” [build] dockerfilePath=”Dockerfile.backend” [build] nixpacksConfigPath=”nixpacks.toml” [build] nixpacksPlan=”messtone/node” [build].nixpacksPlan.phases.setup] nixPkgs=[“…”, “zlib”] [build.nixpacksPlan.phases.install] dependssetup”] cmds =[“cd ../..&& yarn”] [build] nixpacksVersion=”1.13.0″ [deploy] start command=”echo starting” [deploy] numReplicas=2 [deploy] healthcheckPath=”/health” [deploy] healthcheckTimeout=300 [deploy] restartPolicyType=”ON_FAILURE” [deploy] restartPolicyMaxRetries=5 [deploy] cronSchedule=”0 0 ***” railway.toml.file: [environments.production.deploy] startCommand=”echo starting production!” In a railway.json file: {“environments”:{“production”:{“deploy”:{“startCommand”:”echo starting production!”}}}} {“environments”:{“pr”:{“deploy”:{“startCommand”:”echo start command for all pull request!’”}}}} nixpacks.toml file and configure: providers=[“…”, “python”]