TerryMathews

Here we go:

Example files

Any place you see , you need to change it to fit and omit the <>. If something in two differet places like this, make sure they match when you're done as well. Specifically, the postgres user and password in the lemmy docker file and the lemmy.hjson.

Finally, in Google drive the files end in .txt so you can view them. You'll need to correct the file names when you download them if you intend to use them. You should have two docker-compose.yml, one in each of the two directories you create, and one lemmy.hjson.

From a fresh CLI Debian 11 install:

su /sbin/usermod -aG sudo groups apt-get install sudo cd /opt mkdir npm cd npm (copy or create docker-compose.yml) apt-get install docker-compose docker-compose up -d cd /opt mkdir lemmy cd lemmy (copy or create docker-compose.yml and lemmy.hjson) mkdir -p volumes/pictrs chown -R 991:991 volumes/pictrs docker-compose up -d docker ps (verify containers are all running, grab ip address for lemmy container) Configure port forwarding in npm for your lemmy container (npm should be accessible at debian_ip_address:81) Remember to do the custom paths from the various guides. The lemmy port in this guide is 1234.

Please note I am not addressing federation or SSL or true hosting yet. I haven't got that far yet. But if you can get the damn thing running, the last mile shouldn't be too bad.

So I wanted to make a top-level post: I've got a set of example files, and instructions, that will work 100% of the time on Debian. What do you guys think would be the best way to share them? A post here and the files shared on Google Drive? GitHub? Definitely open to suggestions, but I don't want anyone to struggle with it as hard as I have.

This worked for me, with one note:

and need to be lemmy and password if you're using the stock lemmy.hjson file, or the lemmy_lemmy_1 container will get stuck in a reboot loop. There's no define in the stock file in githubusercontent currently for those, so you have to add them by hand.

For security, you have to change these.

Sorry that these are screenshots and not files, but I'm working through Chrome Remote Desktop so my options are a bit limited. This is what I get when I execute 'ansible-playbook -i inventory/hosts lemmy.yml' regardless of whether I have it set to terry@ or root@, and whether I use --become or not.

So, I'm having what I assume is a very basic issue. Going through the ansible install steps, I've created an /etc/ansible/hosts with

[servers] server1 ansible_host=localhost

[all:vars] ansible_python_interpreter=/usr/bin/python3

My understanding is this should work, but ansible all -m ping is failing.

The furthest I got last night, that was where I got stuck as well.

Yes can in a while. At work, I can remote in but not at the moment.

Thanks. I'm hoping to contribute a good walk-through as well once I can get this thing going.

That would be great. I'm not opposed to building, I was actually just sitting here contemplating deep-sixing the whole docker arrangement and just building the services up. That's what I learned back in the day, and to me it feels like Docker and having everything as separate images is just giving me an additional point of failure.

I did. I could never get ansible to work when I was setting up the same machine. If you know how to set the inventory file up for that, I'm all ears.