frold, a non-coder with basic PHP knowledge, seeks to edit Discourse files to experiment with custom tweaks. Confused about locating .rb files on their live server, they wonder if a development box is required. mikechristopher directs them to a beginner’s guide, and pfaffman clarifies that editing files requires a dev environment since production caches changes. frold attempts to navigate the file structure via SSH but struggles to locate files. After setting up a dev environment on macOS following a guide, frold tries to edit amazon_onebox.rb from the onebox gem but can’t find it. techAPJ explains that cloning Discourse core doesn’t include the onebox gem — it must be cloned separately. frold realizes their misunderstanding and feels overwhelmed, questioning the difference between a dev box and live site. mikechristopher explains Discourse relies on modular components, including external gems like onebox. frold now understands but remains confused about which specific files render Amazon data, as the output is identical on their dev box — indicating they’re still targeting the wrong file. The thread reflects the steep learning curve for newcomers trying to modify Discourse’s modular Ruby-based architecture.
I would like to play with the files in discourse - Im not a coder, but I have some tweeks I would like to see if Im able to add. The best way to learn is when you have something you will achieve
I have a little knowledge from php. There you can change a file and see the result of the changes immedealy.
In my discourse server Im not able to finde the .rb files I would like to find. Is that because I need a dev box?
This ruby universe seems to have a steep learning curve… :S
You have the core files and then you have various modules that discourse rely on - some developed by discourse and some not. Onebox is one of those modules.