# Proxy during discourse bootstrap

**URL:** https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880
**Category:** Self-hosting
**Created:** [May 31, 2018, 10:59pm UTC](https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880 "2018-05-31T22:59:31Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![ssvenn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ssvenn/32/86740_2.png) [@ssvenn](https://meta.discourse.org/u/ssvenn)
#### Post date: [June 1, 2018, 9:19pm UTC](https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880/3 "2018-06-01T21:19:18Z")

</div>

If you’re stuck on bootstrapping with the proxy method, I’ve had good success with the cached install method that requires no internet at all on the machine you’re installing on: [Install Discourse on an isolated CentOS 7 server](https://meta.discourse.org/t/how-to-install-discourse-on-an-isolated-centos-7-server/73538)

It works the same on any linux distribution that can run a recent version of docker.  
I recommend creating a shell script for the git clone steps to save a lot of time when it’s time to update the caches, and to make sure you update everything at the same time.  
It quickly becomes a mess if you forget to keep all your plugins in sync with the base discourse.

---

_[View the full topic](https://meta.discourse.org/t/proxy-during-discourse-bootstrap/88880)._