A faster db. Just the regular performance benefits, https://www.postgresql.org/about/news/postgresql-16-released-2715/
Also, Lemmy is built against v16 (now) so at some point it will eventually no longer JustWork
Self Proclaimed Internet user and Administrator of Reddthat
A faster db. Just the regular performance benefits, https://www.postgresql.org/about/news/postgresql-16-released-2715/
Also, Lemmy is built against v16 (now) so at some point it will eventually no longer JustWork
The script will be useless to you, besides for referencing what to do.
Export, remove pg15, install pg16, import. I think you can streamline with both installed at once as they correctly version. You could also use the in place upgrade. Aptly named: pg_upgradeclusters
But updating to 0.19.4, you do not need to go to pg16… but… you should, because of the benefits!
That awkward moment when you are the person they are talking about when running beta in production!
Should be already fixed. I’ve logged out and in on Jerboa.
We rebuilt the Lemmy container with an extra logging patch. Seems build docs need some work? as that’s the only difference in the past 1-2 days, except for moving to postgres 16…
Thanks for the ping.
I’ve gone back to mainline Lemmy. @Morpheus@lemmy.today check now please
Make sure to read the side bar. Support questions go to !askandroid@lemdro.id
See my PR for a new backup script. https://github.com/LemmyNet/lemmy-ansible/pull/210
I’ll get to adding it to the main docs on the weekend.
Tldr, piping your backups via docker is CPU expensive. Directly writing to filesystem in a postgres compatible format with compression is faster and more efficient on the CPU.
My 90GB+ (on filesystem) db compresses to 6GB and takes less than 15 mins.
Been running this since -rc1 & 0.19.1 for the past 13 hours. No issues related to Federation since! just higher CPU load compared to 0.18.x releases.
Thanks for another great release. Suppose I should go fix our ansible ey?
Should be fixed. (It already got merged: https://github.com/LemmyNet/lemmy/pull/4213)
If you don’t see create community in the top next to create post, then your home server doesn’t allow users to create community
No. You have to have an account on that server. (And have to use that account regularly as well, otherwise you won’t see reports about your community)
You make posts.
Don’t forget & in community names and sidebars.
Constantly getting trolled by &
What a hero!
I guess it all depends on what you find interesting. I have the brief extension installed on my browser and whenever I find blogs or people I enjoy if they have an atom/rss feed I subscribe. Over the years you find lots of content.
Some of the random sites I follow:
What happens to the community you made?
Nothing. The community is independent of the users
Or does the community just get stuck without any admin and people can still post in it?
Pretty much. As an admin you can Add/Remove moderators
See this pretty picture of our dropdown menu:
Right? My Linux instance has been the same for 8 years. Same workflows, same no-nonsense. Every time I open the start bar on my work computer and it lags for 5 second to load some bull shit I don’t need I get so mad /rant
Sorry, but I just had to get that off my chest. What’s your setup like?
When you are ok the community you want to subscribe to, there should be a big subscribe button on the top.
But if you are trying to subscribe to communities which are not federated against them you’ll need to currently do what the others say, find the community via web and then it will show up under All.
It’s worth a try, but I doubt it would work. Kbin might have a different authentication flow so it won’t work with any of the Lemmy apps.
Even if the auth flow worked, unless the APIs are exactly the same, then it won’t work as expected anyway :)
That already exists :) join-lemmy.org
Fixed!
And here I thought that I was making it easier for people to have a default selection, rather than actively filtering content. That was not my intention! So sorry, and thankyou @guildz@lemmy.blahaj.zone for helping out.
This is sso support as the client. So you could use any backend that supports the oauth backend (I assume, didn’t look at it yet).
So you could use a forgejo instance, immediately making your git hosting instance a social platform, if you wanted.
Or use something as self hostable like hydra.
Or you can use the social platforms that already exist such as Google or Microsoft. Allowing faster onboarding to joining the fediverse. While allowing the issues that come with user creation to be passed onto a bigger player who already does verification. All of these features are up for your instance to decide on.
The best part, if you don’t agree with what your instance decides on, you can migrate to one that has a policy that coincides with your values.
Hope that gives you an idea behind why this feature is warranted.