- POST route to a controller which calls a model which handles the database stuff, then redirects to..
- the GET route which calls a controller which calls a model which pulls from the database and returns a View which parses the result of the query into a template.
Although you could do it all inside the route closures as well if you wanted... I don't know how much extra overhead there is doing it one way versus the other.
If you want to use Laravel I might suggest picking up one of the starters you can find on github or reading up on MVC, it's really not that hard although it can seem complicated because Laravel puts so much effort into trying to cover every possible model.
Although, given what you're describing, Slim Framework with Twig and a simple class for SQL might be easier.
- POST route to a controller which calls a model which handles the database stuff, then redirects to..
- the GET route which calls a controller which calls a model which pulls from the database and returns a View which parses the result of the query into a template.
Although you could do it all inside the route closures as well if you wanted... I don't know how much extra overhead there is doing it one way versus the other.
If you want to use Laravel I might suggest picking up one of the starters you can find on github or reading up on MVC, it's really not that hard although it can seem complicated because Laravel puts so much effort into trying to cover every possible model.
Although, given what you're describing, Slim Framework with Twig and a simple class for SQL might be easier.