Skip to content

Conversation

@ZogStriP
Copy link
Member

to automatically skip any email-related configuration and enable discourse id

@pmusaraj
Copy link
Contributor

@ZogStriP I ran this twice on a new container, and it failed on this step:

https://github.com/discourse/discourse_docker/blob/master/templates/web.template.yml#L27

Which makes sense. To continue testing, I removed that line from the template, and then the setup continued until:

I, [2025-10-20T18:45:20.881465 #1]  INFO -- :
I, [2025-10-20T18:45:20.890094 #1]  INFO -- : File > /usr/local/bin/configure-letsencrypt  chmod: +x  chown:
I, [2025-10-20T18:45:20.897843 #1]  INFO -- : File > /usr/local/bin/letsencrypt  chmod: +x  chown:
I, [2025-10-20T18:45:20.899064 #1]  INFO -- : > echo "Beginning of custom commands"
I, [2025-10-20T18:45:20.902298 #1]  INFO -- : Beginning of custom commands

I, [2025-10-20T18:45:20.903118 #1]  INFO -- : > rails r "SiteSetting.enable_discourse_id = true"
bundler: failed to load command: script/rails (script/rails)
/var/www/discourse/lib/site_settings/type_supervisor.rb:271:in `validate_value': enable_discourse_id: You must configure Discourse ID credentials ('discourse_id_client_id' and 'discourse_id_client_secret') before enabling this setting. (Discourse::InvalidParameters)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants