Easier setup for selfhosting

[FPGArtktic]

Hello I have just created easier version for self hosting.

https://github.com/FPGArtktic/elixir-cross-referencer-selfhosted.git

[tleb]

Hi @FPGArtktic,

First, I'll clarify my testing local setup:

# build container
docker build -t elixir --build-arg ELIXIR_VERSION=$(git rev-parse --short HEAD) -f ./docker/Dockerfile .

# to index a project
docker run --rm -v ./data/:/srv/elixir-data --entrypoint index elixir /srv/elixir-data musl

# to serve the web interface
docker run --rm --name lxr -v ./data/:/srv/elixir-data elixir

And the prod setup is almost fully public as well. All docker based, see the prod branch which mostly contains the utils/lxr script used to trigger indexing, restart web container and fetch up-to-date Elixir sources.

master...prod

---

Now onto your project!

• Why indexer.sh instead of cron jobs? That's what we use in production.
• One difference I see is offline usage, but that makes no sense to me. Prod is 90G of Git repos & databases. A 90G Docker container is nonsensical. What is your scenario where the indexer cannot access the internet but a different machine (which can access the internet) builds a massive container? Also, you can already index on a different machine from the one serving the web interface.
• Another point is docker-compose. We don't use that in prod, and it is common for every sysadmin to roll their own because everyone has specific needs.

---

It isn't clear what's the point exactly of the project and of this issue? What was missing upstream that meant you needed your own Git repo? I can see two points:

• current README isn't great. I have a local branch that removes a good bunch and simplifies it (focusing on the critical info). I should merge that. Any feedback you have on this topic is appreciated.
• Maybe we could add a docker-compose file to the Elixir project? Would it help others? Every time in issues I asked for people hosting instances to speak up, no one did. That's why I don't bother much with docs, changelogs, versioning, etc. The main instance is our primary focus.

---

Lastly, on a more personal note, I don't mind AI taking over software (or more accurately I try to deal with it) but I like talking to humans. Please use your own voice, or rather keyboard!

Thanks,
Théo