view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
There's some tinkering with their
docker-compose.yml
to make it work. Here's mine you can copy if you want to get it up and running. I don't use nginx or any reverse-proxy btw. All data is saved in their own individual volumes which you can back up:Some of my documents rely on certain packages which didn't come with the Docker image. You will need to run
docker exec sharelatex-sharelatex-1 tlmgr update --self;docker exec sharelatex-sharelatex-1 tlmgr install scheme-full
so that you can render your documents properly if they utilize certain packages.
Optionally—since the full scheme takes about 8 GB and you may not need everything—you can replace
scheme-full
with a different scheme you can find by runningdocker exec sharelatex-sharelatex-1 tlmgr info schemes
The
i
before any scheme name means that it is already installed.Update:
Included a
texlive
volume to save any packages that were installed, so when recreating the containers, they will persist.Are the packages installed to a persistent volume? Or do they need to be reinstalled after recreating the container?
I checked the volumes that I included in the compose file, and looked for either a
texlive
,tlmgr
or apackage
folder and didn't find anything. I think it's safe to assume that you would need to reinstall the packages if you recreated the containers.~~This is a problem that I didn't consider. I will try to make an update to my compose file that will keep the packages persistent.~~
Check above for the update!