You've missed to follow mate. What started this discussion is the way Taiga is mounted with Cloudron technology, we don't have access to these files. 🙂
Your feedback is very welcome, particularly while we are designing the next major Taiga release. Welcoming feedback doesn't mean blindly accepting it. We have our own research and our metrics after 5 years or running this beautiful open source platform and we need to put together all those inputs.
I was not expecting you accept things blindly. These metrics you are talking about are certainly not coming from the branded taiga links in its email templates. And this is what I'm talking about only, emails. Branding emails from the settings inside the app.
I was privileged enough to enjoy early access to the Internet as back as 1995, went into open source in 1996, SuSE 5.1) and I made my career in open source since 2002.
And obviously we both haven't been developing in the same market at all. You, operating systems and in the like. Me, Marketing Technology. For example, I've running one of the first aurotesponders service online, look for "Autoresponse Magic" in Internet Way Back Machine archives. And many more in the like. I'm not saying to brag, only to show we have been online both of us long enough but we have touched two completely different worlds and markets, and approach to the Online Market, which has now become the Market Online. (no kidding)
I've seen quite some stuff over the past 19 years and what you say is true, but may I say I don't like that truth? I mean, white-labeling Taiga is not something that excites me.
Hopefully not and let's hope noone would expect that from you. Me I did not talk about white-labelling Taiga at all, and was talking about having emails of the app to be FREE of Taiga branding.
Mate you need to follow, do not bring me where I haven't touched a word. Thanks 😉
The logs do indicate a database issue and restarting that might have fixed it as well. I guess you restarted mysql as you mentioned, while both apps use postgresql.
Actually the line of:
FATAL: remaining connection slots are reserved for non-replication superuser connections
gives a good indication here. I have seen that recently, that if apps hog onto the postgres connections, it eventually may exhaust the connection pool, then this message is shown. A postgresql service restart resolves this, as it frees up those connection slots.