I do. I just completed pulling the core piped components (piped-backend, -frontend and -prox as well as -html-proxy) from Docker to native installs from the AUR, as well as installing searxng without a venv. Spacebar (the server and client) even have AUR pkgs, but they’re unmaintained… I’m gonna change that.
HHhhmm… Do container/docker install option. This is why it’s probably stagnated in adoption from the selfhosted community.
It needs a container based install, no one likes installing dependencies and crud onto their pristine environments any longer.
I do. I just completed pulling the core piped components (piped-backend, -frontend and -prox as well as -html-proxy) from Docker to native installs from the AUR, as well as installing searxng without a venv. Spacebar (the server and client) even have AUR pkgs, but they’re unmaintained… I’m gonna change that.
It’s just not mentioned prominently https://github.com/spacebarchat/docker
last commit 3yrs ago… seems unmaintained
Docker compose’s don’t really need to be maintained though. As long as the app doesn’t need new components old docker composes should work.
EDIT: Oops, it does look like spacebarchat’s docker images have last been updated over 2 years ago:
https://hub.docker.com/r/spacebarchat/server
EDIT2: Although this is outdated, I think their github repo has an action to autobuild docker images on pushes. Still investigating.
EDIT3: Okay, they don’t seem to be actually ran.
But using nix to build a docker image is pretty cool.
EDIT4: Oh shit, the docker image build workflows were added just 2 hours ago. Of course they haven’t been ran!
Docker support soon, probably.
EDIT5: the workflow ran, but it looks like it’s private for now.
You got my heart racing with the twists!
Right? Reading that was like watching an action movie!
Perhaps more relevantly, the Docker image itself has not been updated in over 2 years: https://hub.docker.com/r/spacebarchat/server
Faster than my edits, I see.
It just depends, however, containers sure do make things a lot cleaner.
It’s weird that the server has a .dockerignore file without a Dockerfile.
Seems like they’re working on Docker build actions right now according to some other comments