Hey guys, I’ve been trying to get Multisite working for a few days now, but no dice. Being self employed is pretty tough just now so I’m trying to consolidate everything onto one VM. I started with a single container site which has been running for awhile. I then moved that behind nginx so I can host some wordpress sites on the same host. SSL is taken care of here. The old discourse forum is working fine, but I now want to add a new forum, using multisite. I’ve followed these instructions: Multisite configuration with Docker And updated the before_bundle_exec: hook with the new forum host name. I guess my questions are: Is it just the second host name that goes in the before_bundle_exec: hook? Does just the first host name go in the env: DISCOURSE_HOSTNAME: variable? Do the smtp settings in the env: section apply to all sites? Here’s what I currently have in app.yml. Any help would be much appreciated. ## this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild app ## ## BE *VERY* CAREFUL WHEN EDITING! ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT! ## visit http://www.yamllint.com/ to validate this file as needed templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) #- "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml" - "templates/web.socketed.template.yml" ## which TCP/IP ports should this container expose? ## If you want Discourse to share a port with another webserver like Apache or nginx, ## see https://meta.discourse.org/t/17247 for details #expose: # - "80:80" # http # - "443:443" # https params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## will be set automatically by bootstrap based on detected RAM, or you can override db_shared_buffers: "1024MB" ## can improve sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LANG: en_US.UTF-8 # DISCOURSE_DEFAULT_LOCALE: en ## How many concurrent web requests are supported? Depends on memory and CPU cores. ## will be set automatically by bootstrap based on detected CPUs, or you can override UNICORN_WORKERS: 4 ## TODO: The domain name this Discourse instance will respond to ## Required. Discourse will not work with a bare IP number. DISCOURSE_HOSTNAME: forum.braidholmplaygroup.co.uk ## Uncomment if you want the container to be started with the same ## hostname (-h option) as specified above (default "$hostname-$config") #DOCKER_USE_HOSTNAME: true ## TODO: List of comma delimited emails that will be made admin and developer ## on initial signup example 'user1@example.com,user2@example.com' DISCOURSE_DEVELOPER_EMAILS: 'foo@braidholmplaygroup.co.uk' ## TODO: The SMTP mail server used to validate new accounts and send notifications # SMTP ADDRESS, username, and password are required # WARNING the char '#' in SMTP password can cause problems! DISCOURSE_SMTP_ADDRESS: smtp.sendgrid.net DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: apikey DISCOURSE_SMTP_PASSWORD:bar #DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true) ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate LETSENCRYPT_ACCOUNT_EMAIL: foo@braidholmplaygroup.co.uk ## The CDN address for this Discourse instance (configured to pull) ## see https://meta.discourse.org/t/14857 for details #DISCOURSE_CDN_URL: //discourse-cdn.example.com ## The Docker container is stateless; all data is stored in /shared volumes: - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log ## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_postgres: - exec: sudo -u postgres createdb b_discourse || exit 0 - exec: stdin: | grant all privileges on database b_discourse to discourse; cmd: sudo -u postgres psql b_discourse raise_on_fail: false - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "alter schema public owner to discourse;"' - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists hstore;"' - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists pg_trgm;"' after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git before_bundle_exec: - file: path: $home/config/multisite.yml contents: | secondsite: adapter: postgresql database: b_discourse pool: 25 timeout: 5000 db_id: 2 host_names: #- forum.braidholmplaygroup.co.uk - forum.tssss.org after_bundle_exec: - exec: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate ## Any custom commands to run after building run: - exec: echo "Beginning of custom commands" ## If you want to set the 'From' email address for your first registration, uncomment and change: ## After getting the first signup email, re-comment the line. It only needs to run once. #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'" - exec: echo "End of custom commands"

[image] Rob_Spencer: it just the second host name that goes in the before_bundle_exec: hook? Yes. [image] Rob_Spencer: Does just the first host name go in the env: DISCOURSE_HOSTNAME: variable? Yes [image] Rob_Spencer: Do the smtp settings in the env: section apply to all sites? Yes. [image] Rob_Spencer: Here’s what I currently have in app.yml. That looks good to me. Did you do a rebuild and see if it works? You’ll need to make the external nginx proxy for the second site just as you have the first one, of course.

Multisite Config

Product Support Self-hosting

pfaffman (Jay Pfaffman) April 1, 2020, 4:45pm 2

Yes.

Yes

Yes.

That looks good to me. Did you do a rebuild and see if it works? You’ll need to make the external nginx proxy for the second site just as you have the first one, of course.

Topic		Replies	Views
Multisite configuration with Docker Self-Hosting docker , explanation , advanced-setup , multisite	0	316944	March 25, 2014
Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy Sysadmins how-to , domains	24	5131	August 27, 2026
Multisite Installation Self-hosting	4	3046	August 6, 2016
How does multisite.yml look? Self-hosting	1	2517	June 17, 2015
Guidance on multi-site setup Self-hosting multisite	0	536	October 9, 2024

Multisite Config

Related topics