- Ruby 58.5%
- JavaScript 35.5%
- HTML 3.1%
- SCSS 2.8%
a446ec9835
This ports the last upload fixes from `script/bulk_import/uploads_importer.rb` that the `disco upload` rework hadn't picked up yet, and fixes two optimizer queries that were reading columns the IntermediateDB doesn't have. From #39703 (S3 access control tags, secure uploads, larger limits): - The site settings step now also sets `max_image_megapixels`, `secure_uploads` and `s3_enable_access_control_tags` from the config file, and I added those three keys to `upload.yml.sample` with short comments. - The fixer's fake upload resource gains `secure?` and `optimized_images: []`, matching what the store needs. When the store is external and the file is still there, a `fix_missing` run now also calls `update_upload_access_control` so it repairs the S3 ACL and tags along the way. I resolve `external?` once in `before_run` instead of per row. From #33523 (optimizer guards): - The missing-upload lookup already returned early on nil, but it produced a generic error with no message. It now records a proper "could not find upload with sha1 …" error that gets reported. - The `e.stacktrace` bug is already gone after the rework: exceptions propagate to the retry policy and are recorded as errors, nothing calls the undefined `stacktrace` method anymore. Optimizer queries against the wrong schema: - The optimizer built its post/avatar id sets from `posts.upload_ids` and `users.avatar_upload_id`. Neither column exists in the current IntermediateDB schema, so both loaders came back empty and no post image or avatar was ever optimized. I rewrote them to read `post_uploads.upload_id` and `users.uploaded_avatar_id`, which is what the schema actually has. Added a spec that runs both loaders against a real IntermediateDB fixture. Note: the in-review posts branch (mt/discourse-posts-step) renames `post_uploads` to `embed_uploads`. Whichever of the two lands second needs to rebase this query onto the surviving table name. Sweep of the rest of the old script against the reworked tasks: the other bits (`OptimizedImage.lock_per_machine = false`, `Jobs.run_immediately!`, the avatar sizes loop, the optimizer's `remote_factor` worker count, and the surplus / missing delete flows) are all already covered by the rework. One difference I noticed but did not change: the old fixer always ran with double the worker count, while the reworked worker count only doubles for an external store. That looks intentional for a local store, so I left it. Also fixes a crash in the fixer that slipped in with the pipeline rework: its `produce` declared the keyword `_emit_result:` — the underscore doesn't mark a keyword as unused, it renames it, so the pipeline's `produce(emit_work:, emit_result:)` call raised ArgumentError as soon as anyone ran --fix-missing. A new contract spec checks all three tasks' `produce` signatures against the pipeline's call so this can't come back. |
||
|---|---|---|
| .agents | ||
| .claude | ||
| .cursor/rules | ||
| .devcontainer | ||
| .github | ||
| .skills | ||
| .vscode | ||
| .zed | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| docs | ||
| frontend | ||
| images | ||
| lib | ||
| log | ||
| migrations | ||
| patches | ||
| plugins | ||
| public | ||
| script | ||
| spec | ||
| stylelint-rules | ||
| test | ||
| themes | ||
| vendor | ||
| .annotaterb.yml | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .ignore | ||
| .jsdoc | ||
| .licensed.yml | ||
| .licensee.json | ||
| .npmrc | ||
| .pnpmfile.cjs | ||
| .prettierignore | ||
| .prettierrc.cjs | ||
| .rspec | ||
| .rspec_parallel | ||
| .rubocop.yml | ||
| .ruby-gemset.sample | ||
| .streerc | ||
| AGENTS.md | ||
| AI-AGENTS.md | ||
| Brewfile | ||
| CLAUDE.md | ||
| CODEOWNERS | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| COPYRIGHT.md | ||
| d | ||
| discourse.sublime-project | ||
| eslint.config.mjs | ||
| Gemfile | ||
| Gemfile.lock | ||
| GEMINI.md | ||
| lefthook.yml | ||
| LICENSE.txt | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| Rakefile | ||
| README.md | ||
| stylelint.config.mjs | ||
| translator.yml | ||
| tsconfig-base.json | ||
| tsconfig.json | ||
| versions.json | ||
The online home for your community.
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:
👉 Discover more communities using Discourse
Development
To get your environment set up, follow one of the setup guides:
- Docker
- Dev Container in VS Code (recommended)
- CLI
- macOS
- Ubuntu/Debian
- Windows
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
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:
- Please read the complete mission statements on discourse.org. Yes we actually believe this stuff; you should too.
- Read and sign the Electronic Discourse Forums Contribution License Agreement.
- Dig into CONTRIBUTING.MD, which covers submitting bugs, requesting new features, preparing your code for a pull request, etc.
- Always strive to collaborate with mutual respect.
- 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 / License
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 W3C’s 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.
We’re 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 couldn’t have done it without you!
