The discussion revolves around configuring a custom private repository of Discourse through Docker. praveendhinwa wants to keep a private Git repository of Discourse code to control the update frequency and avoid breaking plugins in production. However, pfaffman and mpalmer advise against modifying the Discourse core, suggesting instead to develop a plugin or theme.
Alternatively, itsbhanusharma recommends using a stable branch or pinning a particular version in the yml file.
A separate issue is raised by Headless, who wants to restrict users from changing their usernames, which seems to require modifying the Discourse core. Stephen also advises against modifying the core and suggests developing a plugin instead. pfaffman asks if an external SSO is being used, and Headless explains that they are using Roblox’s beta OAuth.
Falco suggests setting the username change period to 0 to disable username changes. Headless confirms that this solution works, but wonders if it’s possible to achieve this without providing an email, as Roblox does not provide one.
We are trying to deploy discourse for our forum through the official docker installation script. We want to keep a private git repo of discourse code. I am not able to figure out a way in the docker script to point to the private repo. I have changed the git clone url in ./image/base/Dockerfile (line 136), and also in the standalone.yml file. Still instead of picking the private repo, it’s picking the github public repo of discourse. Can you please tell me right approach of doing this?
@pfaffman, @mpalmer We are not going to modify the core of discourse at all. We just want to keep it a fixed stable version which can be pulled by docker. This way, we can decide the frequency of pulling the new updates. This can help us avoid breaking of any plugin in production due to changes in discourse.
My use-case is I am using the discourse oauth basic plugin, and I don’t want users to be able to change their usernames. It seems the only way to remove this ability is to change the core of discourse?
Can a plugin remove total access though for changing usernames? Like I am not sure if I can remove the ability on the username route to no longer work via plugin.
I am using Roblox’s beta OAuth. So realistically I don’t want users able to change their usernames at all, and just use the usernames from Roblox.
So realistically I want their Username to become their roblox username, their Name to become their roblox nickname (which both can change on the roblox platform), and their avatar, which can also change.
To all be non-editable by the end-user and automatically update. (atleast on login)
Currently I am using the Oauth 2 basic plugin. Do you suggest I use something else to gain what I am looking for? Basically as SSO?
Even though I am not using the SSO functionality discourse provides as I don’t think I can with roblox? Roblox does not provide a email for the user.
I guess is it even possible for me to do this and not have users change their name,username,avatar while at the same time roblox not providing a email? Since I know when I log in with OAuth it fills in the username, name, and avatar, but I don’t want them to be able to change the username, and name on sign-up. but atleast let them provide a email
