From: John P. R. <ro...@cs...> - 2023-11-14 23:48:12
|
Hi Tonu: In message <CAB...@ma...> , Tonu Mikk writes: >Great, this helps a lot! I was able to run the demo tracker by changing the >line to run the following: >docker run --rm -p 127.0.0.1:8917:8080 --name roundup_demo -v >C://users/tmikk/Documents/roundup-demo/usr/src/app/tracker Are you missing a : between /roundup-demo and /usr? >rounduptracker/roundup:latest demo > >I am not sure though how to run the image on Windows so that I could >configure my own tracker. Just to answer the question for others, you can reconfigure the demo tracker's config.ini changing the web setting and anything else you want to change. If you want to make it accessible under the name "my_tracker" at https://..../my_tracker you run: docker run --rm -p 127.0.0.1:8917:8080 --name roundup_demo -v C://users/tmikk/Documents/roundup-demo:/usr/src/app/tracker rounduptracker/roundup:latest my_tracker=tracker/demo (You could also change the directory name from demo if you wish.) If the argument after the docker image is not one of the special command words: demo shell or admin the docker container starts roundup-server and passes all the arguments after the docker image specification to roundup-server. If there are no arguments it uses 'issue=tracker' and assumes that the tracker home directory is the directory specified with -v. (With demo, the tracker home is placed in a subdirectory of the directory specified with -v.) The proper argument is kind of hinted at in the section: Arguments for roundup-server Once you have initialized your tracker, any arguments placed at the end of the docker run command are passed to the roundup-server. These arguments replace the default arguments of issues=tracker. under: https://roundup-tracker.org/docs/installation.html#running-your-container Would it have helped you if I included a full docker command line in that section? >But I think I will leave it at that for now. I >probably won't be using a Docker container to run Roundup. Fair enough. I don't know how stable docker is on Windows. >I also looked into installing Docker on RedHat 7, but wasn't successful. >Followed a couple of guides, but didn't get it to work. That's sort of what I expected. RedHat 7 is on its last legs at this point. >I will try using the Postgresql backend on RedHat 7 if I can get the >libraries to work. If you are using PostgreSQL, make sure that you either export/dump the database or follow the PostgreSQL directions on executing a proper point-in-time backup of the disk files. I have had a couple of people who were just backing up the PostgreSQL files on a busy tracker without properly configuring/notifying PostgreSQL. They found out the hard way that they didn't really have recent backups of the data 8-(. SQLite has the same concerns over getting a consistent backup. But it appears to be more resilient when you backup the database file by copying. Have a great week. -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. |