# Aws geïmplementeerde discourse haalt assets op uit database url

**URL:** <https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191>\
**Category:** Product Support\
**Tags:** unsupported-install\
**Created:** [16 september 2020 om 11:41 UTC](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191 "2020-09-16T11:41:05Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [17 september 2020 om 08:54 UTC](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191/14 "2020-09-17T08:54:01Z")

</div>

Yes. My recommendation is to use the official discourse and discourse\_docker repositories and implement all changes as plugins.

Using the official discourse\_docker will save you from issues like the one in this topic, and not forking Discourse but keeping all your modifications in separate plugins save you from deviating from the main branch and having to put lots and lots of effort into porting all upstream changes back into your fork.

The learning curve of developing plugins will break even on the effort of merging upstream within a few weeks and from then on it is only more efficient.

When you are using the official Discourse repo then you can also consider managed hosting and people will be more enthusiastic (and/or less expensive) when they need to help you out.

---

_[View the full topic](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191)._
