# Discourse on Azure Container Service?

**URL:** https://meta.discourse.org/t/discourse-on-azure-container-service/63752
**Category:** Self-hosting
**Tags:** unsupported-install, hosting
**Created:** [June 1, 2017, 5:24pm UTC](https://meta.discourse.org/t/discourse-on-azure-container-service/63752 "2017-06-01T17:24:18Z")
**Posts on this page:** 1
**Showing post:** 6

<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: [June 2, 2017, 5:02pm UTC](https://meta.discourse.org/t/discourse-on-azure-container-service/63752/6 "2017-06-02T17:02:49Z")

</div>

Our upgrade process work on the host OS level (the `./launcher rebuild app`) and when we have to update something like Ruby, Nginx, PostgreSQL, Redis, ImageMagick or any of the **many** dependencies we give you a brand new image.

Also upgrading PostgreSQL would be more complicated in this, unless you use the container for web only, and point PostgreSQL and Redis to the compatible Azure managed services.

But I wouldn’t recommend this for someone who just want a small community up. For that our guide to setup on a $10 Digital Ocean or $5 Vultr server is very good and low maintenance. If your site is bigger than that, you should be able to afford [Communiteq](https://www.communiteq.com) (formerly DiscourseHosting) or [our own hosting](https://discourse.org/buy/). You can even use the [Patreon plugin](https://meta.discourse.org/t/configuring-patreon-integration-with-discourse/62380) to help fund a big community hosting fees.

---

_[View the full topic](https://meta.discourse.org/t/discourse-on-azure-container-service/63752)._