Hi, Complete newb here trying to get an installation happening on AWS using EC2 (Ubuntu 16.05LTS), PostgreSQL, Redis. Im following the under 30 minute guide as well as http://stroupaloop.com/blog/discourse-setup-using-aws/ I noticed in the app.yml file, there are no options to specify database. Is it just a point of adding in the following with my settings into the yml file? Thanks in advance Todd DISCOURSE_DB_SOCKET: '' DISCOURSE_DB_NAME: [AWS_POSTGRES_DB_NAME] DISCOURSE_DB_POOL: 15 DISCOURSE_DB_USERNAME: [AWS_POSTGRES_DB_USERNAME] DISCOURSE_DB_PASSWORD: [AWS_POSTGRES_DB_PASSWORD] DISCOURSE_DB_HOST: [AWS_POSTGRES_ENDPOINT] DISCOURSE_REDIS_HOST: [AWS_REDIS_ENDPOINT]

Pretty much and then not mixing in the database.yml file cause you do now want it in the container.

Thanks @sam, Would it t be better to add in the database.yml file?

No, we use GlobalSettings which are either in discourse.conf or ENV for configuration of production.

[image] Tango: AWS Discourse on AWS marketplace is provided by Bitnami. You can go to their official forum and ask your questions.

[image] AbhishekVerma: Discourse on AWS marketplace id provided by Bitnami. Clarification: unsupported Discourse on AWS is provided by Bitnami, if you choose to go that path you must get all your support from Bitnami not meta.discourse.org.

That doesn’t look like it’s using RDS & Elasticache.

@sam how do you “not mix in the database.yml file” Is it just a point of removing the following lines in the app.yml file? “templates/postgres.template.yml” “templates/redis.template.yml” could you please expand Thanks Todd

After making said changes & running ./discourse setup again I am getting error messages FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return # Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development --retry 3 --jobs 4'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]} 2cd1970d5dc16462b89df28ebbd6b880c5640d0b21f8f2283d3b59d8e8695a9f ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Can this be of some help for you? [image] Configure Discourse to use a separate PostgreSQL server Self-Hosting Let’s say you’re using AWS RDS, or an existing PostgreSQL server managed elsewhere. It’s fairly straightforward to get Discourse to use such a setup, without needing to grant superuser privileges to anything that Discourse itself runs. Here’s how. Prerequisites Discourse requires PostgreSQL’s major version to match what we ship with in our docker images; if you try to run on a newer or older version, it might work, but we don’t guarantee it, and if something breaks in the future, you get to …

Installation on AWS

Product Support Self-hosting

Cameron_D (Cameron:D) May 30, 2018, 12:08pm 9

That should be it, yes. The web_only sample should be your basis for the container.

Topic		Replies	Views
Installation on AWS using RDS Self-hosting hosting	6	4921	April 11, 2022
Deploying Discourse on AWS Marketplace	2	1632	May 24, 2016
Aws deployed discourse is fetching assets from database url Product Support unsupported-install	20	2637	November 15, 2020
Can we set up discourse on AWS ECS Self-hosting	1	219	October 18, 2024
Problem setup on AWS: EC2, RDS, ElastiCache Self-hosting unsupported-install	2	2599	September 10, 2017

Installation on AWS

Related topics