3 ms·
"feedback form" to me implies something pretty simple, like a text box. Why not just have an HTML form that saves to a database or file(s)? If you actually mea
by SoftTalker 2y ago
"feedback form" to me implies something pretty simple, like a text box. Why not just have an HTML form that saves to a database or file(s)?
If you actually mean a survey or a lot of questions with multiple-choice answers and nicely tabulated results, then yeah you probably want to just go with a 3rd party backend, or you will end up in a rabbit hole and ultimately reinvent one.
- mmarian 2y agoI agree, it should be something very simple. I ended up trying the database approach in my latest project, but then I started thinking about schema/migrations. I totally missed out the file option that you and @superkuh suggested. It's either that or the Google Forms hack that @stocknoob pointed out, which I'm hoping could be used for ajax requests too.
- SkyPuncher 2y agoWhy would you need a migration for this?
- mmarian 2y agoIn case I change the schema for whatever reason.
- SkyPuncher 2y agoBut why? This data doesn’t need to persist forever. You could literally drop the table (after doing a backup) anytime you need to make a migration.
- mmarian 2y agoI agree the data doesn't need to persist forever, but I don't want to think about backups either. Fussy, I know :)