@catladder/pipeline
Version:
Panter workflow for cloud CI/CD and DevOps
42 lines (38 loc) • 1.1 kB
text/typescript
import type { Config } from "../src";
const config = {
appName: "test-app",
customerName: "pan",
components: {
web: {
dir: "web",
build: {
type: "meteor",
},
deploy: {
type: "google-cloudrun",
projectId: "google-project-id",
region: "europe-west6",
additionalServices: {
// its usually better to create another catladder component for the worker
// but in some legacy cases it might be easier to add an extra service
// notice that you can't use different secrets on the worker, it will receive the same env vars as the normal service
// you can specify extra vars though
worker: {
noCpuThrottling: true,
maxInstances: 1,
minInstances: 1,
command: [
"/bin/sh",
"-c",
"BACKGROUND_JOBS_ENABLED=1 node main.js",
],
},
},
},
},
},
} satisfies Config;
export default config;
export const information = {
title: "Cloud Run: Meteor with Worker",
};