Post by @paul

So far #littleFedi has been great!
Easy to set up with SQLite and just get going really quickly and uses a really tiny amount of resources - great stuff!

Had a little problem federating with my other instances, but that was my fault - I didn't have hairpin NAT in place from and to the VLAN they're all on πŸ™„

Seem to be having another issue with switching to notifications in Tusky crashes the app, but that'll get ironed out I'm sure.

I'd probably also like to switch to postgres at some point (preference not technical) - hopefully there'll be a migration here, otherwise I can probably hopefully migrate manually. If not, so be it - I shall remain on sqlite.

No other concerns to report right now! All is well.

Replying to @paul
GreyLinux
@greylinux @mylittlefedi.capella-ember.uk

@paul@paulwilde.uk
Did you not have hairpin NAT configured for you GoToSocial already ?

@greylinux@mylittlefedi.capella-ember.uk yes, but only from my main vlan I.e. main vlan hairpin nat to fedi vlan was fine.
This is now fedi vlan to fedi vlan and I needed to just put that in place.

Replying to @paul
GreyLinux
@greylinux @mylittlefedi.capella-ember.uk

@paul@paulwilde.uk @paul@paulwilde.uk
ah , I see. I only have the main vlan (LAN) and the "socials" vlan. Similar to you , I had issues where I didn't allow hairpin NAT to the socials vlan itself and the main vlan. So the ``curl --fail https://mylittlefedi.capella-ember.uk/.well-known/nodeinfo`` check wouldn't work .....Doh!

do you run GoToSocial and LittleFedi on different machines?

@greylinux@mylittlefedi.capella-ember.uk yeah, I should have realised it much sooner, and in fact I did check hairpin NAT but failed to remember I recently put my fedi stuff on a different VLAN!

I have gotosocial, snac, honk and now littleFedi all on the same hardware but in FreeBSD jails.
HAProxy runs on a separate machine.

Replying to @paul
GreyLinux
@greylinux @mylittlefedi.capella-ember.uk

@paul@paulwilde.uk
ooh interesting, I wanted to run this little experiment with GTS and LittleFedi on FreeBSD or NetBSD but I didn't want to complicate it further as I have no experience with them. So I settled on Alpine linux , but its a bit Frankenstein at the moment. I have GTS running in docker , Caddy as a natively installed package(previously in docker also) and LittleFedi as a downloaded binary. 😞

I'm a little ashamed, it is a bit of a mess. I may start tickering with NetBSD on a Raspiberry pi zero I have spare and then backup GTS and LittleFedi and switch everything over.

@greylinux@mylittlefedi.capella-ember.uk Alpine linux is still a great base! I have an alpine system running Immich and Frigate.
FreeBSD jails are just so useful, and being able to snapshot them through ZFS so you can ship the entire thing off to another server for backup or recovery reasons is just brilliant.
I have ZFS on Alpine too for the same reasons.

Replying to @paul
GreyLinux
@greylinux @mylittlefedi.capella-ember.uk

@paul@paulwilde.uk
I do run another server , also running Alpine Linux, that hosts Immich , Vaultwarden, Pihole, Jellyfin , Ejabberd and Opencloud. But all local only and accessible by Wireguard remotely.

Replying to @paul
tofeo :verified:
@tofeo @mstdn.social

@paul

How to install #littleFedi ? What is the defaut server ? I want to try on a vps is it possible

Replying to @tofeo@mstdn.social

@tofeo@mstdn.social take a look at the docs at https://littlefedi.org

For a single instance it's real easy to set up, even on a cheap VPS. I think @stefano@littleone.littlefedi.social even tested/uses it on a 1€ per month VPS.
The only real criteria is you will probably need knowledge of how to set up a reverse proxy and how to get TLS certificates (letsencrypt is fine) but other than that it's really simple.

Replying to @paul
tofeo :verified:
@tofeo @mstdn.social

@paul @stefano

I still have a subdomain https : Do I just copy source on the directory?

Replying to @tofeo@mstdn.social

@tofeo@mstdn.social @stefano@littleone.littlefedi.social the documentation explains what you need to do, but you can pretty much download the binary, run littleFedi init, answer all the questions and be up and running.
You will need to use a reverse proxy though - caddy is probably the easiest, but nginx, Apache httpd, haproxy, traffic, etc. Can all do it.

Replying to @paul
tofeo :verified:
@tofeo @mstdn.social
Public fr edited

Today I try to install #littlefedi on #yunohost on an appli my_webapp

Step 1 download the tar
step 2 extract it
step 3 upload the source to a subdirectory
step ? ?? I have 403 Forbidden
nginx

Replying to @tofeo@mstdn.social
tofeo :verified:
@tofeo @mstdn.social

if I ask AI how to install #littlefedi I got this

You need dependancies

sudo apt update
sudo apt install -y git make golang-go

Replying to @tofeo@mstdn.social

@tofeo@mstdn.social
Oh dear, don't"t ask AI about these things, you'll be sent down a bad path straight away

Um... Have you read the documentation yet?
There's a downloadable binary you can just download and run on the server you want to run it.
I can't help you with yunohost though, I know nothing of it.

Replying to @paul

@paul @tofeo@mstdn.social looking at the Yunohost documentation I don't think you can run littleFedi on it until they provide it as a featured application.
"Custom" apps in yunohost can only be HTML, CSS, JS, PHP - littleFedi is none of those. It's effectively it's own service that runs in the background and you reverse proxy incoming traffic to. All you need is a VPS, Caddy and the littleFedi binary really.

EDIT: My mistake - you can, as per Yunohost documentation below
https://doc.yunohost.org/en/admin/apps/custom_apps/#adding-a-reverse-proxy-to-an-app-that-you-manually-installed-for-example-using-docker

Replying to @paul
Stefano Marinelli - littleFedi
@stefano @littleone.littlefedi.social

@paul@paulwilde.uk the sqlite to Postgres path is in the drafts and somehow working, but not that tested, yet, so it'll come. We also have a Postgres to sqlite - you should never be trapped.

@stefano@littleone.littlefedi.social fantastic!
From the effort everyone involved has already put in I was sure something like this may be in the works!

Great job!