Hello,
This is going a little bit beyond the basics, but I'd like to
hear if anyone is running foreman with RailsBaseURI under apache/
passenger:
I'd like to access foreman from http://server.dev.domain.com/foreman
This is my vhost.conf:
<VirtualHost server.dev.domain.com:80>
ServerName server.dev.domain.com
ServerAlias foreman
DocumentRoot /var/www/html
RailsBaseURI /foreman
#<Directory /usr/share/foreman>
#Options -MultiViews
#</Directory>
</VirtualHost>
I have a link: /var/www/html/foreman, pointing to ==> /use/share/
foreman/public
under /use/share/foreman/config/environment.rb I added the line
config.action_controller.relative_url_root = "/foreman"
Foreman comes up ok in the browser via http://server.dev.domain.com/foreman,
however I have foreman.rb (in reports) pointing to http://server.dev.domain.com/foreman,
and when I run puppetd -t from a client, I see the following error in /
var/log/httpd/error_log:
==>> File does not exist: /var/www/html/reports <<===, and there's no
report in foreman of course… 
Can anyone spot what I'm missing here?
Thanks,
Is that a typo? /use ? If not, there's your problem.
R.
···
On 13/12/10 18:12, CraftyTech wrote:
>
> I have a link: /var/www/html/foreman, pointing to ==> /use/share/
> foreman/public
Did you update the foreman.rb report file (in puppets report dir?) you
should change the url to match.
Ohad
···
On Mon, Dec 13, 2010 at 8:12 PM, CraftyTech wrote:
Hello,
This is going a little bit beyond the basics, but I'd like to
hear if anyone is running foreman with RailsBaseURI under apache/
passenger:
I’d like to access foreman from http://server.dev.domain.com/foreman
This is my vhost.conf:
ServerName server.dev.domain.com
ServerAlias foreman
DocumentRoot /var/www/html
RailsBaseURI /foreman
#<Directory /usr/share/foreman>
#Options -MultiViews
#
I have a link: /var/www/html/foreman, pointing to ==> /use/share/
foreman/public
under /use/share/foreman/config/environment.rb I added the line
config.action_controller.relative_url_root = “/foreman”
Foreman comes up ok in the browser via
http://server.dev.domain.com/foreman,
however I have foreman.rb (in reports) pointing to
http://server.dev.domain.com/foreman,
and when I run puppetd -t from a client, I see the following error in /
var/log/httpd/error_log:
==>> File does not exist: /var/www/html/reports <<===, and there’s no
report in foreman of course… 
Can anyone spot what I’m missing here?
Thanks,
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Yes Ohad, that's the foreman.rb file from the puppet reports dir, and
it's pointing to http://server.dev.domain.com/foreman.
how about with the vhost you have on github, is there's any way to
incorporate RailsBaseURI in there…? I'm trying to run foreman from
http://server/foreman, since it's a prod server and something else is
already running on port 80…
Thanks,
···
On Dec 13, 1:16 pm, Ohad Levy wrote:
> Did you update the foreman.rb report file (in puppets report dir?) you
> should change the url to match.
>
> Ohad
>
>
>
>
>
>
>
> On Mon, Dec 13, 2010 at 8:12 PM, CraftyTech wrote:
> > Hello,
>
> > This is going a little bit beyond the basics, but I'd like to
> > hear if anyone is running foreman with RailsBaseURI under apache/
> > passenger:
>
> > I'd like to access foreman fromhttp://server.dev.domain.com/foreman
>
> > This is my vhost.conf:
> >
> > ServerName server.dev.domain.com
> > ServerAlias foreman
> > DocumentRoot /var/www/html
> > RailsBaseURI /foreman
> > #
> > #Options -MultiViews
> > #
> >
>
> > I have a link: /var/www/html/foreman, pointing to ==> /use/share/
> > foreman/public
>
> > under /use/share/foreman/config/environment.rb I added the line
> > config.action_controller.relative_url_root = "/foreman"
>
> > Foreman comes up ok in the browser via
> >http://server.dev.domain.com/foreman,
> > however I have foreman.rb (in reports) pointing to
> >http://server.dev.domain.com/foreman,
> > and when I run puppetd -t from a client, I see the following error in /
> > var/log/httpd/error_log:
> > ==>> File does not exist: /var/www/html/reports < > report in foreman of course...... :)
>
> > Can anyone spot what I'm missing here?
>
> > Thanks,
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Foreman users" group.
> > To post to this group, send email to foreman-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > foreman-users+unsubscribe@googlegroups.com
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/foreman-users?hl=en.
I think its doable, as it sounds from you wrote, its simply that the reports
is going to the wrong path (did you restart your master after that change)?
Alternatively, you can configure apache to listen on another port, and or
use the ssl as well.
Ohad
···
On Mon, Dec 13, 2010 at 8:24 PM, CraftyTech wrote:
Yes Ohad, that’s the foreman.rb file from the puppet reports dir, and
it’s pointing to http://server.dev.domain.com/foreman.
how about with the vhost you have on github, is there’s any way to
incorporate RailsBaseURI in there…? I’m trying to run foreman from
http://server/foreman, since it’s a prod server and something else is
already running on port 80…
Thanks,
On Dec 13, 1:16 pm, Ohad Levy ohadl...@gmail.com wrote:
Did you update the foreman.rb report file (in puppets report dir?) you
should change the url to match.
Ohad
On Mon, Dec 13, 2010 at 8:12 PM, CraftyTech hmmed...@gmail.com wrote:
Hello,
This is going a little bit beyond the basics, but I'd like to
hear if anyone is running foreman with RailsBaseURI under apache/
passenger:
I’d like to access foreman fromhttp://server.dev.domain.com/foreman
This is my vhost.conf:
ServerName server.dev.domain.com
ServerAlias foreman
DocumentRoot /var/www/html
RailsBaseURI /foreman
#<Directory /usr/share/foreman>
#Options -MultiViews
#
I have a link: /var/www/html/foreman, pointing to ==> /use/share/
foreman/public
under /use/share/foreman/config/environment.rb I added the line
config.action_controller.relative_url_root = “/foreman”
Foreman comes up ok in the browser via
http://server.dev.domain.com/foreman,
however I have foreman.rb (in reports) pointing to
http://server.dev.domain.com/foreman,
and when I run puppetd -t from a client, I see the following error in /
var/log/httpd/error_log:
==>> File does not exist: /var/www/html/reports <<===, and there’s no
report in foreman of course… 
Can anyone spot what I’m missing here?
Thanks,
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
<foreman-users%2Bunsubscribe@goog legroups.com>
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
I'll just run it from port 443. Thanks for your help.
···
On Dec 13, 1:34 pm, Ohad Levy wrote:
> I think its doable, as it sounds from you wrote, its simply that the reports
> is going to the wrong path (did you restart your master after that change)?
>
> Alternatively, you can configure apache to listen on another port, and or
> use the ssl as well.
>
> Ohad
>
>
>
>
>
>
>
> On Mon, Dec 13, 2010 at 8:24 PM, CraftyTech wrote:
> > Yes Ohad, that's the foreman.rb file from the puppet reports dir, and
> > it's pointing tohttp://server.dev.domain.com/foreman.
>
> > how about with the vhost you have on github, is there's any way to
> > incorporate RailsBaseURI in there....? I'm trying to run foreman from
> >http://server/foreman, since it's a prod server and something else is
> > already running on port 80....
>
> > Thanks,
>
> > On Dec 13, 1:16 pm, Ohad Levy wrote:
> > > Did you update the foreman.rb report file (in puppets report dir?) you
> > > should change the url to match.
>
> > > Ohad
>
> > > On Mon, Dec 13, 2010 at 8:12 PM, CraftyTech wrote:
> > > > Hello,
>
> > > > This is going a little bit beyond the basics, but I'd like to
> > > > hear if anyone is running foreman with RailsBaseURI under apache/
> > > > passenger:
>
> > > > I'd like to access foreman fromhttp://server.dev.domain.com/foreman
>
> > > > This is my vhost.conf:
> > > >
> > > > ServerName server.dev.domain.com
> > > > ServerAlias foreman
> > > > DocumentRoot /var/www/html
> > > > RailsBaseURI /foreman
> > > > #
> > > > #Options -MultiViews
> > > > #
> > > >
>
> > > > I have a link: /var/www/html/foreman, pointing to ==> /use/share/
> > > > foreman/public
>
> > > > under /use/share/foreman/config/environment.rb I added the line
> > > > config.action_controller.relative_url_root = "/foreman"
>
> > > > Foreman comes up ok in the browser via
> > > >http://server.dev.domain.com/foreman,
> > > > however I have foreman.rb (in reports) pointing to
> > > >http://server.dev.domain.com/foreman,
> > > > and when I run puppetd -t from a client, I see the following error in /
> > > > var/log/httpd/error_log:
> > > > ==>> File does not exist: /var/www/html/reports < > > > report in foreman of course...... :)
>
> > > > Can anyone spot what I'm missing here?
>
> > > > Thanks,
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Foreman users" group.
> > > > To post to this group, send email to foreman-users@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > foreman-users+unsubscribe@googlegroups.com
> >
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/foreman-users?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Foreman users" group.
> > To post to this group, send email to foreman-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > foreman-users+unsubscribe@googlegroups.com
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/foreman-users?hl=en.