I’ve been experimenting with the discourse/discourse_dev Docker image (on Windows 11 laptop) and noticed a small friction point in the developer workflow. When running Discourse in development mode without outbound email configured: 1. You can reach the signup/login page via Ember CLI (localhost:4200). 2. You can create a user account. 3. But login is blocked because email confirmation is required. The workaround seems to be manually activating the account in the Rails console, for example: u = User.find_by(username: "admin") u.approved = true u.email_tokens.update_all(confirmed: true, expired: true) u.save! This works, but I wondered: Is there a recommended developer workflow for bootstrapping the first admin account when email isn’t configured? For example: • Should developers normally configure SMTP even in dev? • Is there a helper task for this (rake admin:create etc.)? • Would it make sense for the dev container to allow first-user login without email confirmation? I’m asking mainly to document a smoother setup process for new developers experimenting with the dev container.

[图片] Ethsim2: Is there a helper task for this (rake admin:create etc.)? Yes there is: [图片]Install Discourse on Ubuntu or Debian for Development Create New Admin To create a new admin, run the following command: bin/rails admin:create Follow the prompts, and a new admin account will be created.

Thanks! That solves it - I hadn’t come across bin/rails admin:create while experimenting with the discourse_dev container. What initially confused me was that the normal UI signup flow works up to the point of creating the account, but login is then blocked by email confirmation if SMTP isn’t configured. For someone just exploring the dev environment, that makes it look like the login flow is broken unless you know about the helper task. It might be helpful to mention bin/rails admin:create explicitly in the development setup docs for the Docker dev container, since new contributors often won’t have SMTP configured.

[图片] Ethsim2: in the development setup docs I am not sure it’s needed in that guide because it says [图片]Install Discourse for development using Docker d/boot_dev --init # wait while: # - dependencies are installed, # - the database is migrated, and # - an admin user is created (you'll need to interact with this) So creating the admin user seems to be part of the workflow already bin/docker/boot_dev 1cb6d36fe echo "pnpm install..." "${SCRIPTPATH}/exec" pnpm install if [ "${initialize}" = "initialize" ]; then echo "Migrating database..." "${SCRIPTPATH}/rake" db:create "${SCRIPTPATH}/rake" db:migrate RAILS_ENV=test "${SCRIPTPATH}/rake" db:migrate echo "Creating admin user..." "${SCRIPTPATH}/rake" admin:create fi

If you do need email access in your dev environment, you can also run mailhog. All you need to do is open a new command line in your Discourse directory and run mailhog. Then if you visit localhost:8025 you can see emails that would normally be sent out, no need to configure anything. [image]

Thanks both - that makes sense. I think the distinction is that the documented d/boot_dev --init path already creates the admin user, so my confusion came from experimenting around the dev environment rather than following that exact init flow end-to-end. The MailHog tip is also helpful. I hadn’t realised the dev setup could capture the confirmation emails locally via mailhog and localhost:8025, which explains the intended workflow if someone does use the normal signup/email-confirmation path. So the smoother mental model seems to be: For the standard Docker dev setup, use d/boot_dev --init and create the admin account when prompted. If testing email/signup flows, run mailhog and view messages at localhost:8025. If needed separately, bin/rails admin:create is the manual helper for creating an admin account. That clears up the confusion - thanks. One small separate question while I’m exploring the dev UI: what are the small icon buttons in the vertical toolbar used for? I can see them in the interface, but I’m not immediately sure whether they are normal user-facing controls, admin shortcuts, or development/debug helpers.

[图片] Ethsim2: One small separate question while I’m exploring the dev UI: what are the small icon buttons in the vertical toolbar used for? Those? [image] That is the dev toolbar. You can toggle safe mode, verbose localization, and upcoming changes. You can also display plugin outlets and blocks. [图片] Introducing Discourse developer toolbar Development When running the latest version of Discourse core in a development environment, you’ll notice a new toolbar on the left-hand-side of the screen: [Developer Tools] This provides one-click access to commonly-needed developer tools. So far, we have: electric_plug Plugin Outlet Debug This shows all plugin outlets, with tooltips showing realtime values of all of the available @outletArgs. This was inspired by the popular plugin outlet locations theme component, and the plugin before it. But un…

开发环境：在没有电子邮件的情况下引导第一个管理员账户的推荐方法是什么？

开发

Moin 2026 年3 月 24 日 22:09 2

是的，有：

话题		回复	浏览量
First Admin GUI utility Feature	5	1403	2014 年1 月 11 日
How to activate admin account in initial setup without email confirmation? Self-hosting email	1	1081	2023 年5 月 1 日
Developing Discourse using a Dev Container Developer Guides	13	20151	2026 年5 月 28 日
First account has no access to admin panel Product Support	7	1630	2016 年5 月 26 日
Create admin account(s) in app.yml without email confirmation Feature	3	2130	2016 年12 月 8 日

开发环境：在没有电子邮件的情况下引导第一个管理员账户的推荐方法是什么？

相关话题