Avelino

@guidiego exist batch operator to `POST` https://docs.postgres.rest/batch-operations/ https://github.com/prest/prest/blob/cfa0f1f80ff7c4fa68bdef716e351156286792ce/controllers/tables.go#L242:L276 needs to implement other http verbs as proposed in this issue, but we should follow the existing standard - it is important...

> GoReleaser - if you pass the tests > Docker Image generate - if you pass the tests Must be runs when it was `git tag` (we use it for...

@nkolster can you implement your “bug” report?

I'm not sure I understand the need, can you give me an example of use? At first it sounds interesting and promising 😃

@aidan-plenert-macdonald so I understood it would be to create a page in the documentation[1] of how to configure pREST on AWS using AWS Lambda, not necessarily an implementation on pREST...

Great point @dariocf1 , no thought was given to other types of status codes Let's plan the implementation, can you propose an implementation?

@george-silva as you have experience can you help us by writing this page?

@alan-francis I like the proposal, We can have a configuration in TOML to call a template file (go template) to use as ETL. Can you implement it?

> @alan-francis @avelino seems it's somehow related to #520 no? @fabriziomello yep

About `log.Fatal` aka `panic`: we should use fatal only where it is necessary to pass some information before the `prestd` server goes up, e.g. database connection invalidates. After the server...