4 ms·
Hmm.. does not look good for the non-Docker setup. The developer replied with "I am deliberately avoiding offering a non-Docker install path" and closed the iss
by mg 4y ago
Hmm.. does not look good for the non-Docker setup. The developer replied with "I am deliberately avoiding offering a non-Docker install path" and closed the issue:
https://github.com/jointakahe/takahe/issues/44 https://github.com/jointakahe/takahe/issues/44
Creating a non-Docker fork would then probably be an uphill battle.
- simonw 4y agoFull quote: > So, I am deliberately avoiding offering a non-Docker install path that is supported right now as it leads to a lot of support burden with different OS package versions and the like! That doesn't mean you can't write and share a script for people who want to install it without Docker. It means that he doesn't want to take responsibility for non-Docker installation scripts as part of the official documentation (yet), because if he did that he'd be on the hook to keep researching and updating those scripts in the future.
- manfre 4y agoThe non docker install path for almost any project is to run the individual scripts from the dockerfile, plus adding the CMD to systemd or similar.