I've created a PostgreSQL backup component Postgres Daily Backups that includes a reasonable default cron schedule in the

railway.json file:

{

"$schema": "https://railway.app/railway.schema.json",

"build": {

"builder": "DOCKERFILE",

"dockerfilePath": "Dockerfile"

},

"deploy": {

"numReplicas": 1,

"cronSchedule": "0 3 * * *",

"restartPolicyType": "ON_FAILURE",

"restartPolicyMaxRetries": 3

}

}

Issue:

When users deploy this service via the template, the cron schedule field appears to be locked/non-modifiable in the template deployment configuration page. This prevents users from customizing the backup

schedule during initial deployment.

Expected Behavior:

I'd like to provide users with a sensible default cron setting (daily at 3 AM UTC) while also giving them the ability to override this value during template deployment, similar to how environment

variables can be modified.

Current Workaround:

Remove the cron setting from the railway.json and add a setting that the user needs to configure to use my template successfully.

Use Case:

For a backup service, different users have different requirements:

- Some want daily backups at 3 AM (the default)

- Others need hourly backups for critical data

- Some prefer weekly backups for less critical systems

Being able to modify the cron schedule during deployment would improve the user experience.

Suggestion:

Could the template deployment UI include an editable field for cronSchedule when it's specified in railway.json, similar to how environment variables are handled?