Milouse

Yes and no. Theoretically, yes you may use one database for all services. Historically it was even an old assumption and some services still ask you for a table prefix to allow various services to use the same db without clashes. However it’s no more recommended and you should absolutely avoid going this way.

But nothing blocks you to have several separate databases on the same server. Here your mysql docker container play the role of a database server. You can use the same container for different services using different databases. Create one specific user/database per service inside your container (you may wrap the official mysql image inside your own image to script its creation), then add it in your docker-compose file and make all your services depend on the same service.

Just for a family and friends I’d go for xmpp. Matrix is still an enormous greavy piece of software, hard to self host if you don’t want to pay for a gigantic server just for it. Also the UI is more like gamer/company chat (discord, slack…), what may not be what your family expect, coming from whatsapp, telegram, or plain sms. In the contrary xmpp is very light and nowadays a lot of tutorial exists on how to configure it, even with voice/video. Plus mobile apps like conversation match the habbits of other messengers.

I’d love to have a link to the wallpaper :)

deleted by creator

You mean on firefox mobile?

I don’t know about the history, but on firefox mobile there is a setting to let you switch from one tab to another when sliding left or right. Maybe you are speaking of that? https://support.mozilla.org/en-US/kb/use-gestures-in-firefox-android#w_switch-tabs-by-swiping-the-address-bar

Thank you very much. I did not receive this email yet, hence my surprise. Time to move my last mailbox on my server.

Where did you read this annoucement?

Half of my passwords are stored with “password manager”, which can be easily plugged to anything. For the rest, I use ansible to manage all my services and thus some secrets are also stored in an ansible vault file. The way my ansible playbooks are organized/commented serves as documentation.