Currently, we let tl-setup create an Apache config file, so that tlclient.cgi can easily be deployed. When the Java Client Applet is removed, tlclient.cgi will only be used for portal integration of the native client. We could consider letting the customer configure Apache etc manually in case they want to use this functionality.
We need to make sure the documentation is sufficient to configure this by hand. Exactly how this needs to be structured is still an open question.
Note the problems in bug 5706 and bug 5576 when documenting this.
Bug 5916 will become obsolete by removing the auto-install steps from tl-setup. The root problem will still remain though, so it should probably still be mentioned in any new installation documentation.
(In reply to comment #3) > Bug 5916 will become obsolete by removing the auto-install steps from tl-setup. > The root problem will still remain though, so it should probably still be > mentioned in any new installation documentation. I've changed my mind after discussing this with Henrik - I will not write anything in the documentation about configuring the firewall for the web server.
> * Apache integration should not be installed with tl-setup > Installation of Web Integration is removed from tl-setup > * It should be possible to install the Apache integration by hand > > > * The manual installation process and prerequisites should be described in the administrators guide > Our documentation describes the requirements and installation process which fulfills the two acceptance criteria mentioned above.
The script install-web-integration does not support an "upgrade", eg. if once run all subsequent calls to the script will fail with: Found Apache configuration directory: /etc/apache2/conf-enabled ERROR: /etc/apache2/conf-enabled/thinlinc.conf already exists! If you wish to install the configuration file to a different file name, set the environment variable APACHE_CONF_NAME to the desired file name and re-run this script. Example: env APACHE_CONF_NAME=thinlinc-portal-integration.conf /opt/thinlinc/share/web_integration/install-web-integration This means if thinlinc.conf is changed with an release it will not be upgrade. Possible solution is to always overwrite and add a note about upgrading in documentation.
(In reply to comment #9) > The script install-web-integration does not support an "upgrade", eg. if once > run all subsequent calls to the script will fail with: > > Found Apache configuration directory: /etc/apache2/conf-enabled > ERROR: /etc/apache2/conf-enabled/thinlinc.conf already exists! > > If you wish to install the configuration file to a different > file name, set the environment variable APACHE_CONF_NAME to the > desired file name and re-run this script. Example: > > env APACHE_CONF_NAME=thinlinc-portal-integration.conf > /opt/thinlinc/share/web_integration/install-web-integration > > This means if thinlinc.conf is changed with an release it will not be upgrade. > > Possible solution is to always overwrite and add a note about upgrading in > documentation. Fixed by r33666.
Finally verified that release notes which also looks good.
