Currently, the prod and dev airtable base IDs are hardcoded in airtable.ts. To support development across multiple developers with different cloned DEV airtable bases, this would be better as an env variable. Also, for prod, there could be different base in the future and no need to have that hard-coded.
Before merging this to production, new AIRTABLE_BASE_ID_PROD env variable should be added to Railway deployment.
Currently, the prod and dev airtable base IDs are hardcoded in airtable.ts. To support development across multiple developers with different cloned DEV airtable bases, this would be better as an env variable. Also, for prod, there could be different base in the future and no need to have that hard-coded.
Before merging this to production, new AIRTABLE_BASE_ID_PROD env variable should be added to Railway deployment.