Foreman install without internet and puppet Server

Problem:
I am trying to find a way to install foreman 1.11 on RHEL 6 server that have no internet connection. But cant find any documentataion that detail the installation steps properly.
I tried to download the rpm and install them but seems there are lot of dependecies.

Expected outcome:
Install foreman without pupper on a server withour internet connection

Foreman and Proxy versions:
1.11
Foreman and Proxy plugin versions:
1.11
Other relevant data:

Error: Package: 1:foreman-installer-1.11.4-1.el6.noarch (foreman-local-1.11)
           Requires: puppet >= 3.0.0
           Available: puppet-2.7.5-1.el6.rf.noarch (rhel-6-rpmforge)
               puppet = 2.7.5-1.el6.rf
           Available: puppet-2.7.9-1.el6.rf.noarch (rhel-6-rpmforge)
               puppet = 2.7.9-1.el6.rf
           Available: puppet-2.7.20-1.el6.rf.noarch (rhel-6-rpmforge)
               puppet = 2.7.20-1.el6.rf
Error: Package: 1:foreman-installer-1.11.4-1.el6.noarch (foreman-local-1.11)
           Requires: puppet >= 3.0.0
           Available: puppet-2.7.5-1.el6.rf.noarch (rhel-6-rpmforge)
               puppet = 2.7.5-1.el6.rf
           Available: puppet-2.7.9-1.el6.rf.noarch (rhel-6-rpmforge)
               puppet = 2.7.9-1.el6.rf
           Installing: puppet-2.7.20-1.el6.rf.noarch (rhel-6-rpmforge)
               puppet = 2.7.20-1.el6.rf
Error: Package: rubygem-apipie-bindings-0.0.14-2.el6.noarch (foreman-local-1.11)
           Requires: rubygem(rest-client) >= 1.6.5
           Available: rubygem-rest-client-1.6.1-1.el6.rf.noarch (rhel-6-rpmforge)
               rubygem(rest-client) = 1.6.1
Error: Package: rubygem-powerbar-1.0.11-11.el6.noarch (foreman-local-1.11)
           Requires: rubygem(ansi) < 1.5.0
Error: Package: rubygem-powerbar-1.0.11-11.el6.noarch (foreman-local-1.11)
           Requires: rubygem(ansi) >= 1.4.0
Error: Package: rubygem-kafo-0.7.5-1.el6.noarch (foreman-local-1.11)

We did rely on EPEL with EL6 and you can find some EL6 Puppet 3 RPMs on http://yum.puppetlabs.com/ but most people have probably forgotten all the details since we haven’t supported a server installation on EL6 for a few years. Why do you want to install such an old version on a platform we’ve stopped supporting?

Foreman 1.11 is very old and contains multiple bugs and security vulnerability. RHEL6 support has also been removed from Foreman since version 1.13.
Foreman indeed has many dependencies, and unless you mirror our repo and the relevant EPEL repos inside your disconnected network you will have to manually handle figuring out all of the dependencies on your own.

In that case which is the Foreman version that you recommend for the the server

# uname -mrs
Linux 2.6.32-696.16.1.el6.x86_64 x86_64

cat /proc/version
Linux version 2.6.32-696.16.1.el6.x86_64 (sandman@node3res7) (gcc version 4.4.7 20120313 (SuSE 4.4.7-18) (GCC) ) #1 SMP Wed Nov 15 02:23:46 EST 2017

[root@intssnbd2adm01 S841177ADM]# cat /proc/meminfo
MemTotal: 24601588 kB
MemFree: 696968 kB
Buffers: 45728 kB
Cached: 8895516 kB
SwapCached: 0 kB
Active: 18945944 kB
Inactive: 4228964 kB

Kindly note, we are trying to install foreman on server without internet connection and later will manage the deployment with Chef.

Looking for your recommendation for Foreman implementaion in this context .

My highest recommendation is to upgrade the server that is going to manage your infrastructure to use an up to date system, not one that has been released almost 2 years ago. If that isn’t possible, at least use the last release that supported this distro (1.12.4).

We don’t generally test installing Foreman in a disconnected environment, so we have no idea what is the complete dependency tree that will be required for allowing offline install. You could try installing this version on a server that runs the same distro with network connectivity to generate a full list of packages needed.

Since you are running on a RHEL host I assume you are a Red Hat customer. Red Hat provides ISO images of Satellite 6, which is based on Foreman, for customers in disconnected setups, but those also dropped support for RHEL6 a couple of versions ago (in Satellite 6.3 iirc).