Changes

From SME Server
Jump to navigationJump to search
104 bytes added ,  18:09, 20 September 2014
no edit summary
Line 1: Line 1: −
<VIP-ire> yep, would should I answer to ?
+
<VIP-ire> yep, would should I answer to ?<br />
<stephdl> hi
+
 
<LayLow1> webapps plays an important role, I was wondering if we can create a wiki page a document the contribs
+
<stephdl> hi<br />
<VIP-ire> well, it's not really a contrib of its own
+
 
<VIP-ire> it's more a kind of framework I use for all my other web based contribs
+
<LayLow1> webapps plays an important role, I was wondering if we can create a wiki page a document the contribs<br />
<LayLow1> correct, it provides crucial functionality, just not to the end user, but under the hood
+
 
<VIP-ire> providing the webapps-update event (against which every other web related stuff links it's templates to be expanded)
+
<VIP-ire> well, it's not really a contrib of its own<br />
<VIP-ire> some alternative apache template to use as virtualhost
+
 
<LayLow1> Yes, and I never got my head around it completely, and the db keys
+
<VIP-ire> it's more a kind of framework I use for all my other web based contribs<br />
<LayLow1> hence my wish to have a wiki page on it
+
 
<LayLow1> but I lack the ability to descibe it correctly
+
<LayLow1> correct, it provides crucial functionality, just not to the end user, but under the hood<br />
<VIP-ire> not that hard ;-)
+
 
<VIP-ire> there's not much in this contrib
+
<VIP-ire> providing the webapps-update event (against which every other web related stuff links it's templates to be expanded)<br />
<VIP-ire> just 2 important things
+
 
<stephdl> We started to look about ipasserelle-im this morning with LayLow1
+
<VIP-ire> some alternative apache template to use as virtualhost<br />
<stephdl> sorry continue VIP-ire
+
 
<VIP-ire> - the webapps-update event (which just expand a few core templates + restart some services)
+
<LayLow1> Yes, and I never got my head around it completely, and the db keys<br />
<VIP-ire> - the WebAppVirtualHost templates, which can be used as more flexible templates for apache vhost
+
 
<LayLow1> right....
+
<LayLow1> hence my wish to have a wiki page on it<br />
<VIP-ire> the most important options are visible here: /etc/e-smith/templates/etc/httpd/conf/httpd.conf/WebAppVirtualHost/50Content
+
 
<LayLow1> and that is where my blackspot is ;-)
+
<LayLow1> but I lack the ability to descibe it correctly<br />
<VIP-ire> basicly, you can create a domaine like this:
+
 
<VIP-ire> db domains set stuff.foo.fr domain Description "My super custom app" Content Primary Nameservers internet TemplatePath WebAppVirtualHost DocumentRoot /opt/stuff RequireSSL enabled
+
<VIP-ire> not that hard ;-)<br />
<VIP-ire> signal-event domain-create stuff.foo.fr
+
 
<VIP-ire> compared with the standard virtualhost templates, you have: the DocumentRoot key, which lets you choose an arbitrary document root instead of having to choose an ibay
+
<VIP-ire> there's not much in this contrib<br />
<VIP-ire> there's the RequireSSL key
+
 
<VIP-ire> there're some more options if you use the ProxyPass directive
+
<VIP-ire> just 2 important things<br />
<VIP-ire> you can also use Authentication=Basic
+
 
<VIP-ire> to ask for a basic auth when reaching this vhost
+
<VIP-ire> - the webapps-update event (which just expand a few core templates + restart some services)<br />
<VIP-ire> and if you're also running smeserver-lemonldap-ng, you can set alternatively Authentication=LemonLDAP
+
 
* LayLow1 remembers something about AliasOnPrimary?
+
<VIP-ire> - the WebAppVirtualHost templates, which can be used as more flexible templates for apache vhost<br />
<LayLow1> Many months ago, we discussed this re shared folders and webdav being reachable on a subdomain and not on /name
+
 
<VIP-ire> AliasOnPrimary is an option I always add to my web based contribs (and is also available for shared folders)
+
<LayLow1> right....<br />
<VIP-ire> if set to disabled
+
 
<VIP-ire> the default /stuff alias on the primary domain won't be added to apache
+
<VIP-ire> the most important options are visible here: /etc/e-smith/templates/etc/httpd/conf/httpd.conf/WebAppVirtualHost/50Content<br />
<VIP-ire> it's only useful if you create a domain which document root points to the app/shared folders
+
 
<LayLow1> stephdl: see why I would like to document all of this :-)
+
<LayLow1> and that is where my blackspot is ;-)<br />
<LayLow1> VIP-ire: thanks
+
 
<LayLow1> VIP-ire: would you call it a tool or a framework?
+
<VIP-ire> basicly, you can create a domaine like this:<br />
<VIP-ire> well, it's not complete enough to call it a framework
+
 
<stephdl> you are right, go LayLow1
+
<VIP-ire> db domains set stuff.foo.fr domain Description "My super custom app" Content Primary Nameservers internet TemplatePath WebAppVirtualHost DocumentRoot /opt/stuff RequireSSL enabled<br />
<LayLow1> ok
+
 
 +
<VIP-ire> signal-event domain-create stuff.foo.fr<br />
 +
 
 +
<VIP-ire> compared with the standard virtualhost templates, you have: the DocumentRoot key, which lets you choose an arbitrary document root instead of having to choose an ibay<br />
 +
 
 +
<VIP-ire> there's the RequireSSL key<br />
 +
 
 +
<VIP-ire> there're some more options if you use the ProxyPass directive<br />
 +
 
 +
<VIP-ire> you can also use Authentication=Basic<br />
 +
 
 +
<VIP-ire> to ask for a basic auth when reaching this vhost<br />
 +
 
 +
<VIP-ire> and if you're also running smeserver-lemonldap-ng, you can set alternatively Authentication=LemonLDAP<br />
 +
 
 +
* LayLow1 remembers something about AliasOnPrimary?<br />
 +
 
 +
<LayLow1> Many months ago, we discussed this re shared folders and webdav being reachable on a subdomain and not on /name<br />
 +
 
 +
<VIP-ire> AliasOnPrimary is an option I always add to my web based contribs (and is also available for shared folders)<br />
 +
 
 +
<VIP-ire> if set to disabled<br />
 +
 
 +
<VIP-ire> the default /stuff alias on the primary domain won't be added to apache<br />
 +
 
 +
<VIP-ire> it's only useful if you create a domain which document root points to the app/shared folders<br />
 +
 
 +
<LayLow1> stephdl: see why I would like to document all of this :-)<br />
 +
 
 +
<LayLow1> VIP-ire: thanks<br />
 +
 
 +
<LayLow1> VIP-ire: would you call it a tool or a framework?<br />
 +
 
 +
<VIP-ire> well, it's not complete enough to call it a framework<br />

Navigation menu