# 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:** 13

<div class="post-metadata">

**Author:** ![ashish\_rawat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ashish_rawat/32/194087_2.png) [@ashish\_rawat](https://meta.discourse.org/u/ashish_rawat)\
**Post date:** [17 september 2020 om 08:27 UTC](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191/13 "2020-09-17T08:27:05Z")

</div>

Hi Richard,

I am on the same team as Vijay. The specific use case we are trying to address here is to fork out Discourse and put in our company’s github. From here, we would build and deploy to AWS. The reason we want to have it in our github is to keep the flexibility of making changes as per our requirements. We would like to contribute back wherever applicable. Since we could not find a dockerfile in the discourse public repo, we ended up creating our own to build the docker image. Further, we use Github actions to deploy the docker to AWS ECS service.

Considering our requirement, do you think we could have taken any other approach?

Thanks.

---

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