On Tuesday 19 May 2009 21:36:40 Peter Amiri wrote:
We've been there, done that!
Sample resin.conf:
--> All your interesting settings stuff goes here! <--
2W
1mb
1mb
1mb
Scott,
Thanks for the input. May be I'm going about this the wrong way. What
is the best practices for setting up shared virtual hosting of Resin.
I basically want to provide Railo (http://www.getrailo.org) hosting.
Railo is a CFML engine that can run on top of any J2EE container.
Right no
On May 18, 2009, at 10:09 AM, Peter Amiri wrote:
> Thank you everyone for your assistance on getting this setup. I now
> have a directory where I can drop individual config files for each
> domain and get them integrated into the resin.conf file using
> . The one issue I have with this is that it
Thank you everyone for your assistance on getting this setup. I now
have a directory where I can drop individual config files for each
domain and get them integrated into the resin.conf file using
. The one issue I have with this is that it requires a
restart of Resin to discover the newly
Peter Amiri schrieb:
>
>
> domainname.com
> /home/path_to_domain/public_html
>
>
> I wanted to know if there was a way to write these individual blocks
> into separate files that got included or imported by the Resin conf
> file.
In addition to the resin:import mechanism,
Try turning on resin logging to "fine" or "finest" and see if it
detects your configuration files.
I don't remember the logging statements, but it should be inside one
of the default resin.conf files that comes with the distribution.
-ck
On May 12, 2009, at 4:33 PM, Peter Amiri wrote:
> Tha
Thanks Scott for all the help. This is how far I've gotten. I have
added the import block to Resin conf file as follows:
*.xml
I have also created a directory at : /var/www/vhosts/resinconf
and placed the following file in it: showmyip.xml
and the fil
On May 12, 2009, at 11:33 AM, Peter Amiri wrote:
> Scott,
>
> Do you know what the syntax of the actual xml files should be? Is
> there a container that should hold the block in the individual
> xml files?
resin:import always uses the containing context for the top-level xml,
because it's lik
Scott,
Do you know what the syntax of the actual xml files should be? Is
there a container that should hold the block in the individual
xml files?
-Peter
On May 12, 2009, at 11:07 AM, Scott Ferguson wrote:
>
> On May 12, 2009, at 10:49 AM, Peter Amiri wrote:
>
>> I am trying to automate th
On May 12, 2009, at 10:49 AM, Peter Amiri wrote:
> I am trying to automate the process of integrating Resin with a cPanel
> hosting environment. For each customer that signs up for a cPanel
> account I need to add the virtual hosting tags to the Resin conf file
> manually. Currently the code bloc
I am trying to automate the process of integrating Resin with a cPanel
hosting environment. For each customer that signs up for a cPanel
account I need to add the virtual hosting tags to the Resin conf file
manually. Currently the code block that is added is similar to this:
d
11 matches
Mail list logo