feat: add env enabling POST to keyword

[quinnlangille]

More for discussion, regarding #57 and #289. I forked the repo, added this ENV to allow the POST /api/keyword route, and it just works. Is there something fundamental I'm missing here or is this a reasonable change?

I plan to use this to enable some automation that pulls keywords from reports already generated by my marketing team, and adds them to tracking here.

Can merge this if the maintainers are interested in having it in main, happy to make any changes / write tests

[gigerIT]

We ran into the same issues and ended up forking SerpBear to address them:
https://github.com/gigerIT/serpbear

Since then, we’ve fixed several critical bugs and also resolved high-severity security issues. We’re continuously improving the project and moving quickly, as we rely on it for our own client work. Keeping the fork stable, up to date, and production-ready is a priority for us.

We’ve also introduced CI (testing + automated releases) to ensure improvements are shipped consistently and reliably.

Multi-user support, outdated documentation, and improved local/city-level tracking are all on our roadmap and being worked on step by step.

If you want to try it out, you can switch to our fork as a drop-in replacement using our Docker image:
gigeritch/serpbear:latest

Sharing this in case it’s useful to others.