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

<div class="post-metadata">

**Author:** ![schleifer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/schleifer/32/86416_2.png) [@schleifer](https://meta.discourse.org/u/schleifer)\
**Post date:** [17 september 2020 om 11:14 UTC](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191/17 "2020-09-17T11:14:47Z")

</div>

Always start with a copy of the discourse\_docker repository. Create an `app.yml` therein.

Use the bootstrap subcommand of the [`launcher` script](http://github.com/discourse/discourse_docker/tree/master/launcher) in your working copy of discourse\_docker to create a docker image. Push the docker image to a docker repository. Deploy that docker image anywhere you like.

Write plugins if you need to. List your custom plugins in the `app.yml` like the other plugins.

---

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