# Discourse in a closed intranet

**URL:** https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449
**Category:** Self-hosting
**Created:** [12. April 2016 um 13:47 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449 "2016-04-12T13:47:14Z")
**Posts on this page:** 7
**Page:** 2

<div class="post-metadata">

### Author: ![nishai](https://avatars.discourse-cdn.com/v4/letter/n/7c8e57/32.png) [@nishai](https://meta.discourse.org/u/nishai)
#### Post date: [28. Februar 2017 um 19:25 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/21 "2017-02-28T19:25:16Z")

</div>

Thank you, you’ve been a great help. I think my biggest hurdle will be the gem bundle install. Besides making a local mirror of the [rubygems.org](http://rubygems.org) which would take gigs of data, I’m struggling to replicate that it my environment

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [28. Februar 2017 um 19:53 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/22 "2017-02-28T19:53:53Z")

</div>

What I did to install Discourse in a closed intranet was setting a proxy (environment variables like http\_proxy, https\_proxy, etc) pointing to my local machine, doing the install and removing the proxy afterwards.

---

<div class="post-metadata">

### Author: ![nishai](https://avatars.discourse-cdn.com/v4/letter/n/7c8e57/32.png) [@nishai](https://meta.discourse.org/u/nishai)
#### Post date: [28. Februar 2017 um 20:50 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/23 "2017-02-28T20:50:07Z")

</div>

I don’t have that option, but there may be a rubygem mirror in the environment that I can point towards.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [28. Februar 2017 um 20:53 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/24 "2017-02-28T20:53:27Z")

</div>

> [@Falco](#):
>
> What I did to install Discourse in a closed intranet was setting a proxy…

Is it not as simple as running `./launcher bootstrap app` on a connected machine and copying over the Docker image (which one apparently can’t do today 🙂 ).

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [28. Februar 2017 um 22:14 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/25 "2017-02-28T22:14:14Z")

</div>

> [@pfaffman](#):
>
> Is it not as simple as running ./launcher bootstrap app on a connected machine

Yes, it really should be. It’s how we do it here a CDCK (albeit the hosting servers _are_ Internet-connected, but they don’t use the network for anything other than downloading the image).

---

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [6. November 2017 um 17:26 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/26 "2017-11-06T17:26:03Z")

</div>

A post was split to a new topic: [How to install Discourse on an isolated CentOS 7 server](https://meta.discourse.org/t/how-to-install-discourse-on-an-isolated-centos-7-server/73538)

---

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [6. November 2017 um 17:26 UTC](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449/27 "2017-11-06T17:26:47Z")

</div>



[Vorherige Seite](https://meta.discourse.org/t/discourse-in-a-closed-intranet/42449.md?page=1)
