# Serve a static site export of discourse while discourse is upgrading

**URL:** https://meta.discourse.org/t/serve-a-static-site-export-of-discourse-while-discourse-is-upgrading/197930
**Category:** Feature
**Created:** [July 22, 2021, 11:24pm UTC](https://meta.discourse.org/t/serve-a-static-site-export-of-discourse-while-discourse-is-upgrading/197930 "2021-07-22T23:24:54Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![balupton](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/balupton/32/255461_2.png) [@balupton](https://meta.discourse.org/u/balupton)
#### Post date: [July 23, 2021, 2:49am UTC](https://meta.discourse.org/t/serve-a-static-site-export-of-discourse-while-discourse-is-upgrading/197930/3 "2021-07-23T02:49:43Z")

</div>

Yeah, be it a DNS change, or booting a temporary docker ngnix container listening on the same port that serves something is the easy part.

Right now the most difficult part of this is a static export with interactivity disabled and a banner added, respecting topic, post, category, index pages (search can be down). Then streamlining this replacement into the upgrade process, however that is easy enough.

Searching the forums for static export, doesn’t really seem it is a thing. I’ve made a Discourse API client already for a prior project, so could code something up that doesn’t emulate the design I guess.

Another factor of serving a static export for this purpose would be ensuring that the static pages are not cached by browsers and not cached by search engines.

* * *

I wonder if [How do I export the complete forum as static html pages? - #3 by wangerin](https://meta.discourse.org/t/how-do-i-export-the-complete-forum-as-static-html-pages/71007/3) would suffice, however seems it would still require interactive elements disabled and a banner injected.

---

_[View the full topic](https://meta.discourse.org/t/serve-a-static-site-export-of-discourse-while-discourse-is-upgrading/197930)._