I’m not sure what you mean by keeping the two systems independent? Let me know if I’m missing some obvious way of solving the problem I’ve laid out, please!
Otherwise, it seems my options are:
-
When a user times out on the main site, before I log them out, call Discourse and check the last_seen value to see if the member has actually been active in the forums (just not doing anything that generates a webhook call). Pros: easy to do. Cons: will generate a lot of API calls, which is something I’m already struggling with and dealing with working around the rate limits.
-
Create my own plugin to ping my main site every now and then, so I can update the user’s last activity time on my main site. Pros: feels more like the “right” solution (to indicate activity with a push message); somewhat elegant. Cons: not easy to implement.
-
Change the logout time on my main site to 2 hours. Pros: easy to implement. Cons: are there any?
-
Don’t worry about it. Users get logged out in the middle of their Discourse session and complain mightily. This is what I have now.
Pros: easy to implement, lol. Cons: a very poor user experience.
Did I miss anything?
Seems like #3 would be a good answer, though I need to think through the ramifications of having a longer logout time on the main site.
I still like #1 as the best choice, but then I have to sort out how to prevent so many damn rate limit issues. I wish there was a way to globally turn off all rate limits in Discourse (and nginx, since I’m using the Discourse Docker install), period, full stop. I don’t need any of them. It’s only my main site talking to my Discourse instance. I don’t allow user API keys and I am the only one with a system API key. It’s a completely closed system and rate limits are doing nothing but (constantly) getting in my way. I guess that’s a different topic.