cjdelisle
cjd
Optimist, believer in the future, believer in people. Political agnostic, hoping to get closer to the truth but don't claim to hold it.
Cjdns founder, working to de-monopolize internet access with mesh networking, decentralized bandwidth market & blockchain micro-payment.
@mosseri
I'm replying to this to see if I can get it to synchronize with other instances on the fedi...
Second, threads posted by me and a few members of the Threads team will be available on other fediverse platforms like Mastodon starting this week. This test is a small but meaningful step towards making Threads interoperable with other apps using ActivityPub – we’re committed to doing this so that people can find community and engage with the content most relevant to them, no matter what app they use.
I will probably be winding down this account.
Folks who are following me here you're welcome to follow me over on @cjd@pkteerium.xyz
These days I'm more of the pleroma-esque mindset that the post button is made to be smashed. If that's not your thing, you can keep following this account only and I'll try to reblog any important messages.
@a1ba@expired.mentality.rip
Wondering if it might be better to just run pleroma in a docker and volume-mount the media dir. I like to be able to hack on it as needed, but for fragile things I tend to prefer keeping them in their own bubbles...
@a1ba@expired.mentality.rip
Thanks, but same error.
@a1ba@expired.mentality.rip
Check the bottom of the pad..
Note:
log: :debug,
show_sensitive_data_on_connection_error: true
Are added by me (trying to debug).
Followed these instructions: https://docs-develop.pleroma.social/backend/installation/alpine_linux_en/#installation up to the end of Install PleromaBE.
However I put it in /home/pleroma and symlinked it to /opt/pleroma, in case that's relevant.
@gme@bofh.social
I try to avoid rebooting
@a1ba@expired.mentality.rip
Here's the console output + postgres log:
https://cryptpad.fr/code/#/2/code/edit/tg6sR7aydDT1tRTYojSyq6xV/
And yes, I did run both. I also dropped the db and ran again to verify it was ok.
@a1ba@expired.mentality.rip
Just what comes to the console when running phx.server or should I find it somewhere ?
No output. But I guess expected? This is a brand new db, just created and then migrated as per the documentation.
@pleb@hunk.city
This is what the postgres log looks like when running it...
@pleb@hunk.city
I'm logging statements on the postgres side and they're definitely coming through, so it is connecting and authenticating. Then something goes wrong...
@gme@bofh.social
Alpine machine, so no systemd.
Crashes running: MIX_ENV=prod mix phx.server
I created the db and ran the migration.
@helene
New db so there's really no reason it should be having migration issues...
At least fchan finally figured out how to actually do anonymity. IIRC a few years ago I looked around and there was some "chan" but it was just a pleroma skin and everyone had a name 🤦♂️
Hmm, now it's still crashing but without the ConnectionError.
Just this:
13:44:37.240 [notice] Application pleroma exited: exited in: Pleroma.Application.start(:normal, [])
** (EXIT) an exception was raised:
** (RuntimeError) could not lookup Ecto repo Pleroma.Repo because it was not started or it does not exist
Pleroma Q:
I'm getting:
13:38:47.821 [info] Postgrex.Protocol (#PID<0.928.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.1040.0> exited
and then a crash running `mix phx.server`
Connection to postgres works, postgres says:
STATEMENT: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1)
Then:
DEBUG: unexpected EOF on client connection
Ideas ?