Making some changes to the code

Support
1

This may be a stupid question, but I always try to gather information as
much as possible. We have a running foreman server and would like make some
changes to the code. It is a rather bold move, but I'm taking the changes
from a foreman branch. Is there anything I should know before diving in
(services to restart, directories…)? I've just started managing the
server so any input would be appreciated.
Thanks

2

> This may be a stupid question, but I always try to gather information as
> much as possible.

No question is stupid :slight_smile:

> We have a running foreman server and would like make some
> changes to the code. It is a rather bold move, but I'm taking the changes
> from a foreman branch. Is there anything I should know before diving in
> (services to restart, directories…)? I've just started managing the server
> so any input would be appreciated.
> Thanks

If you're just backporting changes, and it's a package-based install
(rpm / deb) then the key things are:

  • code in /usr/share/foreman (and potentially /usr/share/foreman-proxy)
  • Foreman runs in Apache, so you can restart that or just "touch
    ~foreman/tmp/restart.txt"
  • The proxy has it's own service, so you can service restart that

There's plenty more to know, as Foreman is pretty complex software. If
you can share more about what you're doing, or what problems you hit,
then we can help you more. Be aware that we do try to backport things
where possible (up to a point), so you may hit issues with something
we decided couldn;t be backported. Again, more details will lead to
more information :wink:

If you're doing more than just backporting stuff, then consider
writing a Foreman Plugin - this will encapsulate your changes and keep
them safe across package upgrades and so on.

Finally, it's worth being aware of the foreman-dev mailing list and
#theforeman-dev IRC channel for assistance with development related
queries, should you need code-change-related help.

Hope that helps!
Greg

··· On 25 October 2015 at 15:35, ghidu wrote:
3

Thanks Greg for your help. I have already made the changes (taken from one
of Shlomi commits) and so far so good.

··· On Sunday, October 25, 2015 at 5:35:00 PM UTC+2, ghidu wrote: > > This may be a stupid question, but I always try to gather information as > much as possible. We have a running foreman server and would like make some > changes to the code. It is a rather bold move, but I'm taking the changes > from a foreman branch. Is there anything I should know before diving in > (services to restart, directories...)? I've just started managing the > server so any input would be appreciated. > Thanks >