I forked the Discourse repository on GitHub. How can I replace it with the existing Discourse installation on my site? I have tried everything, but I encountered errors each time. I added my own Discourse repository from GitHub to the app.yml file, but I couldn’t proceed due to errors. Even when I managed to make the changes, it always reinstalled the original Discourse. How can we properly execute this process? [image] Can't change repo in discourse docker Development In the past, I’ve done it by editing app.yml like this: hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/scossar/localized-categories - git clone https://github.com/scossar/dictionary-card-onebox - exec: cd: $home cmd: # changes start here - git remote remove origin - git config --remove-section branch.ma…

[image] kuaza: due to errors [image] kuaza: I encountered errors each time It helps to be specific.

Upon re-examination, I made a modification to the discourse I was analyzing, and I noticed that this change is visible on the update page within the admin panel. I am now updating it; if the adjustment functions correctly, I will revise this message accordingly. These are the settings in my app.yml file, which I have rebuilt without encountering any errors. However, upon subsequent review, the modifications I made are not visible, although Discourse continues to operate flawlessly. 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: cd: /var/www/discourse cmd: - sudo -u discourse git remote set-url origin https://github.com/KilicSelcuk/discourse.git - sudo -u discourse git fetch origin - sudo -u discourse git checkout origin/main - sudo -u discourse git remote set-branches --add origin main - sudo -u discourse git remote set-branches origin tests-passed - sudo -u discourse git reset --hard origin/main - exec: echo "End of custom commands"

[image] kuaza: the modifications I made are not visible So when you do view source and look at the 6th line or so, does the commit hash in the version string correspond to the latest commit in your forked repository?

I believed I had completed the task, but it appears to be ineffective. The latest update visible on the admin update page is: https://github.com/KilicSelcuk/discourse/commit/e44347414a8325ec25e5892c35bcd889d39a6668. However, the actual modifications I made are reflected here: Commits · KilicSelcuk/discourse · GitHub. In essence, the changes I implemented are not visible on the update page. Additionally, when I perform a rebuild, it does not incorporate my repository’s updates. If the changes had been applied, they would be visible. My most recent configuration is as follows: ## Any custom commands to run after building run: - exec: echo "Beginning of custom commands" ## To set the 'From' email address for your initial registration, uncomment and modify: ## After receiving 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: cd: /var/www/discourse cmd: - sudo -u discourse git remote set-url origin https://github.com/KilicSelcuk/discourse.git - sudo -u discourse git fetch origin - sudo -u discourse git checkout origin/main - sudo -u discourse git remote set-branches --add origin main # - sudo -u discourse git remote set-branches origin tests-passed # - sudo -u discourse git branch -u origin/main - sudo -u discourse git reset --hard origin/main Resolving this issue would be beneficial. I couldn’t find a helpful resource on the forum, but it might serve as a guiding reference for those who follow.

[image] kuaza: I forked the Discourse repository on GitHub That’s usually a bad idea. You should make changes in a plugin.

Indeed, I was originally doing this, but once the plugin was integrated into the core, I am no longer able to modify it. Unfortunately, the suggested solutions also proved ineffective: Overriding user_guardian.rb in a plugin (no fork necessary!) - #24

If you have forked a plugin, then you should rm the included plugin and clone your version. I think I’ve told told you about this in another topic. You definitely want to fork just the plugin and not the whole app and all the other plugins.

I encounter an error whenever I attempt to install the plugin. If I have more time, I will try again: Overriding user_guardian.rb in a plugin (no fork necessary!) - #24

That is the way to solve your problem. If you have an error, and want help, you should say exactly what the error is, and include the plugins section of your yml file and a link to your forked plugin.

Regrettably, I am diligently striving to resolve the issue; I have shared the fault in this matter as well, yet I have not yet found a solution. Overriding user_guardian.rb in a plugin (no fork necessary!) - #24

I forked the Discourse repository on GitHub. How can I replace it with the existing Discourse installation on my site?

Product Support

pfaffman (Jay Pfaffman) August 23, 2025, 10:26pm 6

That’s usually a bad idea. You should make changes in a plugin.

Topic		Replies	Views
How my changes can take effect on Discourse with docker Product Support	9	1991	June 15, 2015
Can't change repo in discourse docker Development	9	3702	February 15, 2018
Deploy custom Discourse repository via docker Self-hosting docker	6	757	January 30, 2024
How to install customized discourse on docker? Development	1	873	May 10, 2017
Procedure to update standard plugins Development	7	303	November 23, 2025

I forked the Discourse repository on GitHub. How can I replace it with the existing Discourse installation on my site?

Related topics