Problem / use case
I'm currently using the Railway's deployment ID as the schema for my ponder instances. However, it makes redeploys to fully reindex, even when no coding changes.
ponder start --views-schema=anticapture --schema=$RAILWAY_DEPLOYMENT_ID
Proposed solution
I wonder if there is a way to use Ponder's internal buildId as the schema name itself, so that only actual code changes would trigger a reindex.