I'd strongly recommend leaving passenger alone for now until we've got
the packages sorted for RC2. You won't be able to run both the
puppetmaster and Foreman in the same instance in the setup you describe
as they'd use different Ruby versions. We're packaging passenger 4 in
order to support this.
You should find the standalone "foreman" service is running and
listening on port 3000, visit http://fqdn:3000/ and you should get the
web interface. Please note the login bug in the announcement e-mail
too, you'll need to run the reset permissions rake task before the login
will work first time!
···
On 27/05/13 22:25, Ronaldo M wrote:
> I installed foreman 1.2 RC1 on CentOS 6
> Although install using foreman-installer went fine I'm having trouble
> getting the foreman web interface to work so I can login.
>
> Installed foreman without ssl/passenger but by doing so I also don't
> have an apache foreman configuration (/etc/httpd/conf.d/foreman.conf).
> Tried to create a foreman.conf in /etc/httpd/conf.d but without
> passenger, I don't get a login page. With passenger i get rake errors
> because puppet also uses passenger but not SCL.
>
> Any ideas/suggestions on how i can create an httpd conf that show me the
> foreman login page while I'm not using ssl/passenger?
>
> Id like to have all foreman components running on one machine.
–
Dominic Cleal
Red Hat Engineering
Thanks that was it 
Because I have using passenger for a long while, I all forgot about port
3000 that foreman itself is using 
···
Op maandag 27 mei 2013 23:29:19 UTC+2 schreef Dominic Cleal het volgende:
>
> On 27/05/13 22:25, Ronaldo M wrote:
> > I installed foreman 1.2 RC1 on CentOS 6
> > Although install using foreman-installer went fine I'm having trouble
> > getting the foreman web interface to work so I can login.
> >
> > Installed foreman without ssl/passenger but by doing so I also don't
> > have an apache foreman configuration (/etc/httpd/conf.d/foreman.conf).
> > Tried to create a foreman.conf in /etc/httpd/conf.d but without
> > passenger, I don't get a login page. With passenger i get rake errors
> > because puppet also uses passenger but not SCL.
> >
> > Any ideas/suggestions on how i can create an httpd conf that show me the
> > foreman login page while I'm not using ssl/passenger?
> >
> > Id like to have all foreman components running on one machine.
>
> I'd strongly recommend leaving passenger alone for now until we've got
> the packages sorted for RC2. You won't be able to run both the
> puppetmaster and Foreman in the same instance in the setup you describe
> as they'd use different Ruby versions. We're packaging passenger 4 in
> order to support this.
>
> You should find the standalone "foreman" service is running and
> listening on port 3000, visit http://fqdn:3000/ and you should get the
> web interface. Please note the login bug in the announcement e-mail
> too, you'll need to run the reset permissions rake task before the login
> will work first time!
>
> --
> Dominic Cleal
> Red Hat Engineering
>
