Symbolic links in httpd_config.xml

zellster

Well-Known Member
#1
LSWS 3.3.3 Std, Linux 32-bit

Sample entry in httpd_config.xml:

<vhTemplate>
<name>EasyRailsWithSuEXEC</name>
<templateFile>$SERVER_ROOT/conf/templates/rails.xml</templateFile>
<listeners>Default</listeners>
<member>
<vhName>RubyVHost</vhName>
<vhDomain>127.0.0.1</vhDomain>
<vhAliases>foo.bar.com</vhAliases>
<vhRoot>/opt/my_app/current</vhRoot>
</member>
</vhTemplate>

/opt/my_app/current is a symbolic link, pointing to the actual release number (e.g. /opt/my_app/1.01). After some amount of time, including reloads, the <vhRoot/> text changes from the symbolic link to the actual directory name.

<vhTemplate>
<name>EasyRailsWithSuEXEC</name>
<templateFile>$SERVER_ROOT/conf/templates/rails.xml</templateFile>
<listeners>Default</listeners>
<member>
<vhName>RubyVHost</vhName>
<vhDomain>127.0.0.1</vhDomain>
<vhAliases>foo.bar.com</vhAliases>
<vhRoot>/opt/my_app/1.0.1</vhRoot>
</member>
</vhTemplate>

Changing the symbolic link to a new release no longer works as expected, due to the hard-coding of the last release in httpd_config.xml. Is the readlink-behavior necessary?
 

mistwang

LiteSpeed Staff
#2
I did not find any where in the web console to replace a symbolic link with the real path.
Can you change it back to the link? Will it change back to the real path? How can you reproduce it?
 
Top