Manu
Manu
I'm seeing the same issue and error in my own installations and some [PikaPods.com](https://www.pikapods.com) users have reported them. Workaround is to limit history days (to 14 or 30 days) and...
I'm guessing the solution would be to use a real database if one has "real" data. Or to limit the data, like I'm doing right now https://github.com/louislam/uptime-kuma/issues/1397#issuecomment-1172847138
> The only solution IMO is running a proper DB, which as I understand is difficult to do because of the way uptime Kuma is built Why is it difficult...
Done with all the app setup and anyone can now run SerpBear with a few clicks. Again, good job. Looks already quite good for the early stage of development. https://www.pikapods.com/pods?run=serpbear
Great! Let me know if I can help with anything. Like writing up steps, doing a docs PR, etc.
Sure, we usually update every 7 to 10 days, when an update was out for at least 3 days. Need to double-check if Serpbear's release feed is hooked up.
Speaking of: Some version tags would be nice and maybe a short changelog for Github releases. Since you already have tags, pushing those to Docker is simple. Anyways. I've subscribed...
Google env var was already added.
Hey @towfiqi, is there a repo to edit the docs and add this? Would be the second hosted option besides fly.io (which needs a bit more setup work).
Sure thing. Was actually working on SerpBear today, to make sure adding the Google key as env var works as expected. Instructions following the existing style: ``` # Deploying to...