On Mon, 11 Dec 2017 11:51:13 +0100, Bo Berglund <bo.bergl...@gmail.com> wrote:
>Maybe the tiny server is not connected to the eth0 public address? >Localhost seems suspicious to me. I ended up editing the /usr/lib/viewvc/bin/standalone.py file on the line specifying the binding: host = sys.platform == 'mac' and '192.168.xxx.xxx' or 'engineering-lx' # '127.0.0.1' or 'localhost' After this I could see the repository through the basic ViewVC glasses on my PC! Much improved view over the svn built-in Apache view :) But standalone.py is not what I want to run anyway, so I need to plow through the immense installation configuration to enable VieVC integration into Apache2... Or is there a quyick way to get the standalone.py version become the way ViewVC serves out the repository via Apache2? Note: My CVS users are all working through the WinCVS application from the CVSGui project that died about 10 years ago... None is comfortable with command line work or Linux for that matter, all are on Windows workstations. So I need to give them some GUI style tools to convince of a migration to Subversion. Maybe VisualSVN on Windows can fulfill this? -- Bo Berglund Developer in Sweden
