Noob-question: How do I run foreman as https://server/foreman

Support
1

Hi all,

this is probably pretty easy for you guys.

How do I configure it to run as https://myserver/foreman?

Running the foreman-installer the foreman-gui will appear at
https://myserver by default.
I tried to set the "foreman_url" parameter to https://myserver/foreman but
this didn't work.

Thanks for your help!

Denny

2

Hello,

> How do I configure it to run as https://myserver/foreman?

the only supported and recommended deployment is at /

Note it is not recommended to install other software on the Foreman
instance other than we expect.

> Thanks for your help!

It should be technically possible, but you are on your own. Try to
deploy with the defaults using our installer and then change Apache2
configuration. Rails should handle that using the RAILS_ROOT_SOMETHING
option, but keep in mind we don't test with that setup. There will be
dragons.

··· -- Later, Lukas #lzap Zapletal
3

Not the answer I wanted to hear, but thank you for that statement :slight_smile:

··· Am Mittwoch, 18. Februar 2015 12:55:29 UTC+1 schrieb Lukas Zapletal: > > Hello, > > > How do I configure it to run as https://myserver/foreman? > > the only supported and recommended deployment is at / > > Note it is not recommended to install other software on the Foreman > instance other than we expect. > > > Thanks for your help! > > It should be technically possible, but you are on your own. Try to > deploy with the defaults using our installer and then change Apache2 > configuration. Rails should handle that using the RAILS_ROOT_SOMETHING > option, but keep in mind we don't test with that setup. There will be > dragons. > > -- > Later, > Lukas #lzap Zapletal >
4

I don't think answer was entirely correct. I think nightly already support
sub-uri deployment, you can run installer like this

foreman-installer
–foreman-foreman-url="https://$FQDN/foreman"
–foreman-proxy-foreman-base-url="https://$FQDN/foreman" \

you must specify the correct FQDN. There might be some glitches but I run
Foreman on sub-uri from day 1 and it works generally.

On the other hand, it's not a good idea to run many other services, foreman-
installer deletes apache conf.d/* files it does not know, so you should
probably try --noop mode first…

Hope this helps

··· On Wednesday 18 of February 2015 04:27:45 Denny Gebel wrote: > Not the answer I wanted to hear, but thank you for that statement :) > > Am Mittwoch, 18. Februar 2015 12:55:29 UTC+1 schrieb Lukas Zapletal: > > Hello, > > > > > How do I configure it to run as https://myserver/foreman? > > > > the only supported and recommended deployment is at / > > > > Note it is not recommended to install other software on the Foreman > > instance other than we expect. > > > > > Thanks for your help! > > > > It should be technically possible, but you are on your own. Try to > > deploy with the defaults using our installer and then change Apache2 > > configuration. Rails should handle that using the RAILS_ROOT_SOMETHING > > option, but keep in mind we don't test with that setup. There will be > > dragons.

–
Marek

5

A good use case for having some what to make URI adjustments is to allow
for local repos for the OS install medias that you want to use. Whether
that's changing the foreman uri, or being able to handle additional
locations, I can't say, but at one point I tried to set something like that
up and it didn't go well. Not so much that I want to run other
"applications" but don't want to have to build a server or goto the
internet for those install medias.

··· On Wednesday, February 18, 2015 at 9:26:30 AM UTC-5, Marek Hulan wrote: > > On Wednesday 18 of February 2015 04:27:45 Denny Gebel wrote: > > Not the answer I wanted to hear, but thank you for that statement :) > > > > Am Mittwoch, 18. Februar 2015 12:55:29 UTC+1 schrieb Lukas Zapletal: > > > Hello, > > > > > > > How do I configure it to run as https://myserver/foreman? > > > > > > the only supported and recommended deployment is at / > > > > > > Note it is not recommended to install other software on the Foreman > > > instance other than we expect. > > > > > > > Thanks for your help! > > > > > > It should be technically possible, but you are on your own. Try to > > > deploy with the defaults using our installer and then change Apache2 > > > configuration. Rails should handle that using the RAILS_ROOT_SOMETHING > > > option, but keep in mind we don't test with that setup. There will be > > > dragons. > > I don't think answer was entirely correct. I think nightly already support > sub-uri deployment, you can run installer like this > > foreman-installer \ > --foreman-foreman-url="https://$FQDN/foreman" \ > --foreman-proxy-foreman-base-url="https://$FQDN/foreman" \ > > you must specify the correct FQDN. There might be some glitches but I run > Foreman on sub-uri from day 1 and it works generally. > > On the other hand, it's not a good idea to run many other services, > foreman- > installer deletes apache conf.d/* files it does not know, so you should > probably try --noop mode first... > > Hope this helps > > -- > Marek >