# Cloudflare setup and other post-migration tasks

**URL:** <https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557>\
**Category:** Migration\
**Created:** [January 22, 2023, 9:41pm UTC](https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557 "2023-01-22T21:41:09Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [January 24, 2023, 2:19am UTC](https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557/8 "2023-01-24T02:19:47Z")

</div>

> [@Crius](#):
>
> What do I need to do to set cloudflare up so it doesn’t bother discourse?

It depends on what role (if any) you want Cloudflare to play.

If you just want to use Cloudflare as DNS then make sure the orange cloud is disabled for the ‘a’ record of the forum.

If you want to actually send Discourse traffic across Cloudflare’s network and are ok with the additional latency it adds then at the minimum create a page rule to ‘Disable Performance’ for the entire forum domain. None of the Cloudflare performance optimizations are recommended and have been known to break sites.

Note that there’s a Cloudflare template which needs to be added to your app.yml, it will pass the CF-Connecting-IP as the client IP, so that you aren’t seeing everyone as originating from a node on their network.

If you aren’t using object-based storage and do run with the orange cloud enabled you _can_ create a caching rule for your assets path.

---

_[View the full topic](https://meta.discourse.org/t/cloudflare-setup-and-other-post-migration-tasks/252557)._