Changes

From SME Server
Jump to navigationJump to search
m
categorisation
Line 1: Line 1: −
== Web Application Tutorial ==
+
{{Needs review}}
 +
{{Incomplete}}
 +
== Web Application Redirect Tutorial ==
 +
 
 +
 
 +
{{Warning box|The method outlined in this Howto, whilst being functional, may cause some as yet to be defined odd problems with the primary domain, so you are advised to use it with discretion. Further testing needs to be carried out to correctly identify the exact source and nature of these problems. Please test these modifications on your system and if you notice issues report them to the bugtracker. '''Work is continuing to develop a better method, see the discussion page.'''}}
 +
 
    
===Overview===
 
===Overview===
Line 5: Line 11:  
This Howto gives a practical example of redirecting (virtual) domains to web applications located in the /opt/... folder.  
 
This Howto gives a practical example of redirecting (virtual) domains to web applications located in the /opt/... folder.  
   −
It utlises information published in http://wiki.contribs.org/Web_Application_RPM and applies it to an example installation of Joomla CMS using http://wiki.contribs.org/Joomla
+
It utilises information published in http://wiki.contribs.org/Web_Application_RPM and applies it to an example installation of Joomla CMS using http://wiki.contribs.org/Joomla
    
The same concepts will apply to other web applications or content installed in /opt/....
 
The same concepts will apply to other web applications or content installed in /opt/....
Line 37: Line 43:     
It is taken from http://wiki.contribs.org/Web_Application_RPM  
 
It is taken from http://wiki.contribs.org/Web_Application_RPM  
Webserver Templates - a workaround to enable the application to be located in a domain or subdomain rootwith joomla
+
Webserver Templates - a workaround to enable the application to be located in a domain or subdomain root with joomla
    
  {
 
  {
Line 43: Line 49:  
   return "    # joomla-status is disabled.\n"
 
   return "    # joomla-status is disabled.\n"
 
           unless $status eq 'enabled';
 
           unless $status eq 'enabled';
 
+
 
   my $domain = $joomla{'domain'} || "disabled";
 
   my $domain = $joomla{'domain'} || "disabled";
 
   return "    # no hostname or domain for joomla defined\n"
 
   return "    # no hostname or domain for joomla defined\n"
 
           if $domain eq 'disabled';
 
           if $domain eq 'disabled';
 
+
 
   my $DocRoot = "/opt/joomla";
 
   my $DocRoot = "/opt/joomla";
 
+
 
   $OUT  = "";
 
   $OUT  = "";
 
   $OUT .= "\n";
 
   $OUT .= "\n";
Line 77: Line 83:  
  expand-template /etc/httpd/conf/httpd.conf
 
  expand-template /etc/httpd/conf/httpd.conf
 
  sv h /service/httpd-e-smith
 
  sv h /service/httpd-e-smith
 +
 +
{{Warning box|This example refers to installation using the joomla rpm. When using the SiteMaker contrib, or doing additional installations of joomla or installing other rpms that do not setup default configuration db entries, it will be necessary to manually create the service entry and other db entries. In those cases you would do something like the following, as necessary.
 +
 +
config set joomla2 service
 +
config setprop joomla2 DbName joomla2
 +
config setprop joomla2 DbPassword joomla2passwordxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 +
config setprop joomla2 DbUser joomla2user
 +
config setprop joomla2 Name Joomla2
 +
config setprop joomla2 PublicAccess global
 +
expand-template /etc/httpd/conf/httpd.conf
 +
sv h /service/httpd-e-smith
 +
 +
Make sure you use the correct mysql db name, password & user, as already created for the joomla2 (or whichever) db in mysql.}}
      Line 136: Line 155:  
     URL=cms
 
     URL=cms
 
     status=enabled
 
     status=enabled
  −
      
===Reference links===
 
===Reference links===
Line 149: Line 166:  
----
 
----
 
[[Category:Howto]]
 
[[Category:Howto]]
 +
[[Category:Development Tools]]

Navigation menu