0
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2026-08-11 02:59:07 +08:00
A platform for community discussion. Free, open, simple. https://www.discourse.org
  • Ruby 58.5%
  • JavaScript 35.5%
  • HTML 3.1%
  • SCSS 2.8%
Find a file
2026-06-18 07:06:19 +00:00
.agents DEV: symlink to skills (#38573) 2026-03-18 09:41:56 +11:00
.claude DEV: symlink to skills (#38573) 2026-03-18 09:41:56 +11:00
.cursor/rules DEV: update various ai agent configurations (#34192) 2025-08-11 10:08:41 +10:00
.devcontainer DEV: Bump devcontainer image (#40684) 2026-06-09 15:02:51 +01:00
.github Revert "experiment[219]: Switch The Core System Job's Headless Browser From Full Chromium's "New Headless" Mode (Pinned By channel: :chromium Since The May-2025 Chrome-To-Chromium Migration) To Playwright's Purpose-Built chromium-headless-shell Of The Identical Build Revision 1217, Installed By A New Core-Scoped Workflow Step Beside The Image's --no-shell Bake And Selected By A Binary-Availability Check In SystemDrivers So Dev Boxes, Plugin/Theme System Jobs, And Headful Debugging Keep Full Chromium Byte-Identically (PLAYWRIGHT_FULL_CHROMIUM=1 Restores It Anywhere), Because Interleaved A/B On create_invite Measures The Shell At -2.0% Wall On All Four Pairs (15.84 vs 16.17s Median) And ~8% Less Browser CPU (17.8/17.8/18.6 vs 19.3/19.6s Plus A 27.5s Control Outlier) With Two Fewer Crashpad Processes Per Browser Across The 10 CPU-Saturated Workers — Shipped After This Session's Deep Falsification Of The Bigger Compile-Cache Family: Chromium Never Code-Caches The Production Build's ES-Module Bundles At Any Level (Persistent-Profile Disk Cache Consumed Only 168KB Of Classic Scripts After 9 Loads, Same-Tab Same-Isolate Re-Navigation Still Recompiles ~400-600ms CPU Every Round), Killing The addCompilationCache/Persistent-Context/Kept-Page-CPU Leads And Retroactively Explaining iter-213/217's Renderer-Reuse Wash — Validated Green On The Shipping Bytes: 152/152 Ten-File 4-Worker turbo_rspec With Complete 258-Entry Runtime Log, 62/62 Social Auth Serial Through The Second Driver Connection, 29/29 Seed-5309 Five-Class CI=1 Basket, 51/51 Risky-API Specs (WebAuthn CDP, CSV Downloads, Clipboard, webm Video Upload, Canvas/Lightbox), And The Kill Switch Verified Relaunching Full Chrome Plus Crashpad" 2026-06-12 03:08:13 +00:00
.skills DEV: Make upcoming change CSS classes opt-in (#40669) 2026-06-10 12:12:58 +10:00
.vscode DEV: Replace JS build system with Rolldown (#35963) 2026-05-29 11:11:55 +01:00
.zed DEV: add Zed editor configuration (#36958) 2026-01-06 23:30:45 +01:00
app DEV: move desktop sidebar-section CSS to common, remove desktop css index (#40803) 2026-06-11 15:09:09 -04:00
bin Revert "experiment[15]: Scale System Test Workers From 10 To 16 By Cloning Parallel Test Databases In bin/turbo_rspec" 2026-06-12 01:09:09 +00:00
config UX: combine group visibility and access configuration (#40758) 2026-06-11 11:20:29 -04:00
db FEATURE: Modernize Graphviz implementation (#40720) 2026-06-11 11:42:23 +01:00
docs Enhance DModal API documentation with arguments and blocks (#40399) 2026-06-02 16:53:16 +02:00
frontend DEV: Bundle chart.js into a single async chunk (#40796) 2026-06-11 17:22:24 +01:00
images
lib experiment[216]: Re-Land The Never-CI-Falsified Six-Mechanism Stack On The Rebased Base (capyq + IPC Fold + MiniRacer GC No-Op + Race-Fixed Runtime Split + Stable-Wait Skip + Avatar Stub + Honest Content-Keyed Digests, Atop The iter-199 Promoted Layer Of Production Ember Build + Vendored-Driver Soft Context Reset + Rack become.json sign_in That The Rebase Replay Dropped Along With Every Other Patch From iter-146 Onward) By Materializing git merge-tree's Clean Auto-Merge Of iter-215's Measured Sha 1a086e06cb With New Base b5ba10eb5f And Byte-Verifying Every Path Against The Merge Tree, Because iter-215's Three Green Draws (401/437/466, Run-1 The Best In Loop History) Were pull_request Merge-Commit Runs That Already Tested Exactly This Composition — Stack Merged With Main's Spec-Infra Restructure (SystemDrivers, MessageBusTestSync, Extracted Helpers) — Modulo Only Two Commits Outside The Core System Job (Migrations Tooling + discourse-ai Plugin Under LOAD_PLUGINS=0), With All Five 3-Way Merge Points Auto-Merged And Hand-Reviewed, origin/main Verified Still At The New Base So PR Merge Runs Work Again (The Killed Prior-216 push: Trigger Intentionally Not Re-Landed), And Re-Validated Green On The Shipping Bytes: 63/63 Five-Class Seed-5309 Basket, 8/8 Locale Defined-Order, 62/62 Social Auth Through The Wrapper's Second Driver Connection, And 131/131 4-Worker turbo_rspec With A Complete 258-Entry Parent-Merged Runtime Log 2026-06-12 01:09:22 +00:00
log
migrations MT: Add disco check — a single entrypoint for all schema and converter checks 2026-06-11 21:27:17 +02:00
patches DEV: Replace JS build system with Rolldown (#35963) 2026-05-29 11:11:55 +01:00
plugins FEATURE: Allow AI agents to add notes to reviewables (#40807) 2026-06-11 17:57:01 -03:00
public DEV: move discourse gifs to core (#40162) 2026-06-10 11:35:44 +04:00
script DEV: Automatic upcoming change status report and PR creation (#40291) 2026-06-11 15:19:15 +10:00
spec Revert "experiment[219]: Switch The Core System Job's Headless Browser From Full Chromium's "New Headless" Mode (Pinned By channel: :chromium Since The May-2025 Chrome-To-Chromium Migration) To Playwright's Purpose-Built chromium-headless-shell Of The Identical Build Revision 1217, Installed By A New Core-Scoped Workflow Step Beside The Image's --no-shell Bake And Selected By A Binary-Availability Check In SystemDrivers So Dev Boxes, Plugin/Theme System Jobs, And Headful Debugging Keep Full Chromium Byte-Identically (PLAYWRIGHT_FULL_CHROMIUM=1 Restores It Anywhere), Because Interleaved A/B On create_invite Measures The Shell At -2.0% Wall On All Four Pairs (15.84 vs 16.17s Median) And ~8% Less Browser CPU (17.8/17.8/18.6 vs 19.3/19.6s Plus A 27.5s Control Outlier) With Two Fewer Crashpad Processes Per Browser Across The 10 CPU-Saturated Workers — Shipped After This Session's Deep Falsification Of The Bigger Compile-Cache Family: Chromium Never Code-Caches The Production Build's ES-Module Bundles At Any Level (Persistent-Profile Disk Cache Consumed Only 168KB Of Classic Scripts After 9 Loads, Same-Tab Same-Isolate Re-Navigation Still Recompiles ~400-600ms CPU Every Round), Killing The addCompilationCache/Persistent-Context/Kept-Page-CPU Leads And Retroactively Explaining iter-213/217's Renderer-Reuse Wash — Validated Green On The Shipping Bytes: 152/152 Ten-File 4-Worker turbo_rspec With Complete 258-Entry Runtime Log, 62/62 Social Auth Serial Through The Second Driver Connection, 29/29 Seed-5309 Five-Class CI=1 Basket, 51/51 Risky-API Specs (WebAuthn CDP, CSV Downloads, Clipboard, webm Video Upload, Canvas/Lightbox), And The Kill Switch Verified Relaunching Full Chrome Plus Crashpad" 2026-06-12 03:08:13 +00:00
stylelint-rules DEV: Exploring a token system (#38700) 2026-04-23 13:47:45 -05:00
test DEV: Clean up smoke-test (#40066) 2026-05-15 12:28:41 +02:00
themes FIX: Horizon > Apply create-topic-label transformer to Horizon sidebar button (#40730) 2026-06-10 12:12:28 +02:00
vendor experiment[216]: Re-Land The Never-CI-Falsified Six-Mechanism Stack On The Rebased Base (capyq + IPC Fold + MiniRacer GC No-Op + Race-Fixed Runtime Split + Stable-Wait Skip + Avatar Stub + Honest Content-Keyed Digests, Atop The iter-199 Promoted Layer Of Production Ember Build + Vendored-Driver Soft Context Reset + Rack become.json sign_in That The Rebase Replay Dropped Along With Every Other Patch From iter-146 Onward) By Materializing git merge-tree's Clean Auto-Merge Of iter-215's Measured Sha 1a086e06cb With New Base b5ba10eb5f And Byte-Verifying Every Path Against The Merge Tree, Because iter-215's Three Green Draws (401/437/466, Run-1 The Best In Loop History) Were pull_request Merge-Commit Runs That Already Tested Exactly This Composition — Stack Merged With Main's Spec-Infra Restructure (SystemDrivers, MessageBusTestSync, Extracted Helpers) — Modulo Only Two Commits Outside The Core System Job (Migrations Tooling + discourse-ai Plugin Under LOAD_PLUGINS=0), With All Five 3-Way Merge Points Auto-Merged And Hand-Reviewed, origin/main Verified Still At The New Base So PR Merge Runs Work Again (The Killed Prior-216 push: Trigger Intentionally Not Re-Landed), And Re-Validated Green On The Shipping Bytes: 63/63 Five-Class Seed-5309 Basket, 8/8 Locale Defined-Order, 62/62 Social Auth Through The Wrapper's Second Driver Connection, And 131/131 4-Worker turbo_rspec With A Complete 258-Entry Parent-Merged Runtime Log 2026-06-12 01:09:22 +00:00
.annotaterb.yml DEV: Upgrade Rails to version 8.0.2 2025-07-22 09:59:44 +02:00
.autoresearch_marker [autoresearch] iter 219 confirmation 4 2026-06-12 02:59:51 +00:00
.ci-validate-marker DEV: validation marker round-1 2026-06-18 07:06:19 +00:00
.editorconfig
.git-blame-ignore-revs DEV: Add nested module style commit to .git-blame-ignore-revs 2026-03-20 10:08:56 +01:00
.gitattributes
.gitignore DEV: Replace JS build system with Rolldown (#35963) 2026-05-29 11:11:55 +01:00
.ignore
.jsdoc
.licensed.yml DEPS: Bump oauth from 1.1.3 to 1.1.5 (#40263) 2026-06-04 01:06:17 +02:00
.licensee.json DEV: Bump vitest and vite (#40450) 2026-06-08 10:29:44 +01:00
.npmrc DEV: prevent pnpm to ask for update (#34808) 2025-09-15 20:11:12 +02:00
.pnpmfile.cjs DEV: Overhaul typechecking configuration (#35794) 2025-11-12 12:54:34 +00:00
.prettierignore DEV: Add a script for generating external types in discourse-types (#37095) 2026-03-09 20:37:43 +01:00
.prettierrc.cjs
.rspec
.rspec_parallel
.rubocop.yml DEV: Enable Style/RedundantSelf rubocop rule (#40098) 2026-05-19 19:27:45 +02:00
.ruby-gemset.sample
.streerc DEV: Move discourse-calendar to core (#33570) 2025-07-15 16:38:05 +02:00
AGENTS.md DEV: update various ai agent configurations (#34192) 2025-08-11 10:08:41 +10:00
AI-AGENTS.md DEV: Optimise number of lint calls in AI-AGENTS.md (#40594) 2026-06-05 11:48:49 +08:00
AUTORESEARCH.md [autoresearch] mark branch + drop irrelevant CI workflows — DO NOT MERGE 2026-06-12 01:09:08 +00:00
Brewfile Add image optimization and utility tools to Brewfile (#35940) 2025-12-16 16:35:19 +11:00
CLAUDE.md DEV: update various ai agent configurations (#34192) 2025-08-11 10:08:41 +10:00
CODEOWNERS DEV: Add Block API for declarative, validated UI extension points (#36810) 2026-02-25 17:36:43 -03:00
config.ru
CONTRIBUTING.md
COPYRIGHT.md
d
discourse.sublime-project
eslint.config.mjs DEV: Replace JS build system with Rolldown (#35963) 2026-05-29 11:11:55 +01:00
Gemfile experiment[216]: Re-Land The Never-CI-Falsified Six-Mechanism Stack On The Rebased Base (capyq + IPC Fold + MiniRacer GC No-Op + Race-Fixed Runtime Split + Stable-Wait Skip + Avatar Stub + Honest Content-Keyed Digests, Atop The iter-199 Promoted Layer Of Production Ember Build + Vendored-Driver Soft Context Reset + Rack become.json sign_in That The Rebase Replay Dropped Along With Every Other Patch From iter-146 Onward) By Materializing git merge-tree's Clean Auto-Merge Of iter-215's Measured Sha 1a086e06cb With New Base b5ba10eb5f And Byte-Verifying Every Path Against The Merge Tree, Because iter-215's Three Green Draws (401/437/466, Run-1 The Best In Loop History) Were pull_request Merge-Commit Runs That Already Tested Exactly This Composition — Stack Merged With Main's Spec-Infra Restructure (SystemDrivers, MessageBusTestSync, Extracted Helpers) — Modulo Only Two Commits Outside The Core System Job (Migrations Tooling + discourse-ai Plugin Under LOAD_PLUGINS=0), With All Five 3-Way Merge Points Auto-Merged And Hand-Reviewed, origin/main Verified Still At The New Base So PR Merge Runs Work Again (The Killed Prior-216 push: Trigger Intentionally Not Re-Landed), And Re-Validated Green On The Shipping Bytes: 63/63 Five-Class Seed-5309 Basket, 8/8 Locale Defined-Order, 62/62 Social Auth Through The Wrapper's Second Driver Connection, And 131/131 4-Worker turbo_rspec With A Complete 258-Entry Parent-Merged Runtime Log 2026-06-12 01:09:22 +00:00
Gemfile.lock experiment[216]: Re-Land The Never-CI-Falsified Six-Mechanism Stack On The Rebased Base (capyq + IPC Fold + MiniRacer GC No-Op + Race-Fixed Runtime Split + Stable-Wait Skip + Avatar Stub + Honest Content-Keyed Digests, Atop The iter-199 Promoted Layer Of Production Ember Build + Vendored-Driver Soft Context Reset + Rack become.json sign_in That The Rebase Replay Dropped Along With Every Other Patch From iter-146 Onward) By Materializing git merge-tree's Clean Auto-Merge Of iter-215's Measured Sha 1a086e06cb With New Base b5ba10eb5f And Byte-Verifying Every Path Against The Merge Tree, Because iter-215's Three Green Draws (401/437/466, Run-1 The Best In Loop History) Were pull_request Merge-Commit Runs That Already Tested Exactly This Composition — Stack Merged With Main's Spec-Infra Restructure (SystemDrivers, MessageBusTestSync, Extracted Helpers) — Modulo Only Two Commits Outside The Core System Job (Migrations Tooling + discourse-ai Plugin Under LOAD_PLUGINS=0), With All Five 3-Way Merge Points Auto-Merged And Hand-Reviewed, origin/main Verified Still At The New Base So PR Merge Runs Work Again (The Killed Prior-216 push: Trigger Intentionally Not Re-Landed), And Re-Validated Green On The Shipping Bytes: 63/63 Five-Class Seed-5309 Basket, 8/8 Locale Defined-Order, 62/62 Social Auth Through The Wrapper's Second Driver Connection, And 131/131 4-Worker turbo_rspec With A Complete 258-Entry Parent-Merged Runtime Log 2026-06-12 01:09:22 +00:00
GEMINI.md DEV: update various ai agent configurations (#34192) 2025-08-11 10:08:41 +10:00
lefthook.yml [autoresearch] mark branch + drop irrelevant CI workflows — DO NOT MERGE 2026-06-12 01:09:08 +00:00
LICENSE.txt
package.json DEPS: Bump lefthook from 2.1.8 to 2.1.9 (#40622) 2026-06-08 07:12:15 +08:00
pnpm-lock.yaml DEV: move discourse gifs to core (#40162) 2026-06-10 11:35:44 +04:00
pnpm-workspace.yaml DEV: Replace JS build system with Rolldown (#35963) 2026-05-29 11:11:55 +01:00
Rakefile
README.md DEV: Link to Docker CLI documentation (#40375) 2026-05-28 22:10:18 +02:00
stylelint.config.mjs DEV: Exploring a token system (#38700) 2026-04-23 13:47:45 -05:00
translator.yml DEV: Add discourse-footnote client.yml translator config (#37178) 2026-01-16 15:23:50 +00:00
tsconfig-base.json DEV: Add Block API for declarative, validated UI extension points (#36810) 2026-02-25 17:36:43 -03:00
tsconfig.json DEV: Add a script for generating external types in discourse-types (#37095) 2026-03-09 20:37:43 +01:00
versions.json DEV: Begin development of v2026.6.0-latest (#40362) 2026-05-28 10:56:24 +02:00

The online home for your community.

github-readme

You can self-host Discourse on your own infrastructure. But if you'd rather skip the setup, maintenance, and server management, we offer official Discourse hosting.

👉 Learn more about Discourse hosting

Discourse is a 100% open-source community platform for those who want complete control over how and where their site is run.

Our platform has been battle-tested for over a decade and continues to evolve to meet users needs for a powerful community platform.

With Discourse, you can:

  • 💬 Create discussion topics to foster meaningful conversations.

  • Connect in real-time with built-in chat.

  • 🎨 Customize your experience with an ever-growing selection of official and community themes.

  • 🤖 Enhance your community with plugins, from chatbots powered by Discourse AI to advanced tools like SQL analysis with the Data Explorer plugin.

To learn more, visit discourse.org and join our support community at meta.discourse.org.

Here are just a few of the incredible communities using Discourse:

discourse-communities

👉 Discover more communities using Discourse

Development

To get your environment set up, follow one of the setup guides:

Before you get started, ensure you have the following minimum versions: Ruby 3.4+, PostgreSQL 15, Redis 7.

For more information, check out the Developer Documentation.

Setting up Discourse

If you want to set up a Discourse forum for production use, see our Discourse Install Guide.

If you're looking for official hosting, see discourse.org/pricing.

Requirements

Discourse supports the latest, stable releases of all major browsers and platforms:

Browsers Tablets Phones
Apple Safari iPadOS iOS
Google Chrome Android Android
Microsoft Edge
Mozilla Firefox

Additionally, we aim to support Safari on iOS 16.4+.

Built With

  • Ruby on Rails — Our back end API is a Rails app. It responds to requests RESTfully in JSON.
  • Ember.js — Our front end is an Ember.js app that communicates with the Rails API.
  • PostgreSQL — Our main data store is in Postgres.
  • Redis — We use Redis as a cache and for transient data.
  • BrowserStack — We use BrowserStack to test on real devices and browsers.

Plus lots of Ruby Gems, a complete list of which is at /main/Gemfile.

Contributing

Build Status

Discourse is 100% free and open source. We encourage and support an active, healthy community that accepts contributions from the public including you!

Before contributing to Discourse:

  1. Please read the complete mission statements on discourse.org. Yes we actually believe this stuff; you should too.
  2. Read and sign the Electronic Discourse Forums Contribution License Agreement.
  3. Dig into CONTRIBUTING.MD, which covers submitting bugs, requesting new features, preparing your code for a pull request, etc.
  4. Always strive to collaborate with mutual respect.
  5. Not sure what to work on? We've got some ideas.

We look forward to seeing your pull requests!

Security

We take security very seriously at Discourse; all our code is 100% open source and peer reviewed. Please read our security guide for an overview of security measures in Discourse, or if you wish to report a security issue.

Security fixes are listed in the release notes for each version.

The Discourse Team

The original Discourse code contributors can be found in AUTHORS.MD. For a complete list of the many individuals that contributed to the design and implementation of Discourse, please refer to the official Discourse blog and GitHub's list of contributors.

Copyright 2014 - 2025 Civilized Discourse Construction Kit, Inc.

Licensed under the GNU General Public License Version 2.0 (or later); you may not use this work except in compliance with the License. You may obtain a copy of the License in the LICENSE file, or at:

https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Discourse logo and “Discourse Forum” ®, Civilized Discourse Construction Kit, Inc.

Accessibility

To guide our ongoing effort to build accessible software we follow the W3Cs Web Content Accessibility Guidelines (WCAG). If you'd like to report an accessibility issue that makes it difficult for you to use Discourse, email accessibility@discourse.org. For more information visit discourse.org/accessibility.

Dedication

Discourse is built with love, Internet style.

For over a decade, our amazing community has helped shape Discourse into what it is today. Your support, feedback, and contributions have been invaluable in making Discourse a powerful and versatile platform.

Were deeply grateful for every feature request, bug report, and discussion that has driven Discourse forward. Thank you for being a part of this journey—we couldnt have done it without you!