Hi! First of all, thanks for sharing this suite of tools.

Would you be open to allowing the table name used for storing migrations to be customised? This would be useful if you're using Postgres schemas, so that __migrations__ becomes schema1.__migrations__, for example.

Also, when do you typically run migrations? Do you have any experience with automatically running migrations after the function is deployed?

Thanks again!