-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interest in Docker image #79
Comments
Hey thanks for contributing this. I don't use Docker myself, so if we put it in this repo I don't be able to maintain it. :( So maybe a separate repo is best, unless someone vows to help maintain it. Just let me know! :) |
I have been trying to get a docker version running myself. I literally found this repo yesterday. I am going to try the above instructions now. |
This needs a bit more work. On the first run, I am getting the following error.
|
This does need a bit more work yes, but your docker container is working correctly. You can do
And see that it's working, you just have to go through the general |
Maybe put in a contrib directory?
|
Hi, thanks for the interesting project @mholt! As I'm not a go developer, I wrote up some simple docker things to get this running for me locally without making a full go dev environment. In case it helps anyone else, here they are:
Dockerfile
docker-compose.yml
Usage
/media/external/Timeliner
above) and editdocker-compose.yml
to match.timeliner.toml
in the timerliner directory.docker-compose run timeliner
to runtimeliner
commands.If you're running this on a home server, as I am, you can go through the OAuth flow as normal by using a local port forward (e.g.
ssh -L 8008:localhost:8008 my-server
).These things are still kind of rough and would need a bit of polishing before they would be worth making them more accessible, but I wanted to first see if there was any interest in cleaning these up to either put them directly in this repository, or put them in a separate repository, and build images that could be deployed to docker hub or some other place that hosts docker images. I did see #69 but that was a year ago so things may have changed since.
The text was updated successfully, but these errors were encountered: