discourse/config/dev_defaults.yml
Isaac Janzen 37942cb8bb
DEV: Convert admin-incoming-email modal to component-based API (#22701)
- Convert `admin-incoming-email` modal to component-based API
- Testing that the modal was working in local development was extremely challenging due to the need for `rejected` and `bounced` emails. Something that is not easy to stub in a local dev environment. To make this process more smooth for future developers I have added a new rake task:

```
desc "Creates sample email logs"
task "email_logs:populate" => ["db:load_config"] do |_, args|
  DiscourseDev::EmailLog.populate!
end
```

That will generate fully functional email logs in development to be toyed with.

<img width="787" alt="Screenshot 2023-07-20 at 3 27 04 PM" src="https://github.com/discourse/discourse/assets/50783505/47b3fe34-cd7e-49a5-8fe6-768c0fbd1aa2">
2023-07-20 16:31:20 -05:00

44 lines
796 B
YAML

site_settings:
tagging_enabled: true
verbose_discourse_connect_logging: true
seed: 1
start_date: 2020-01-01
auth_plugin_enabled: true
allow_anonymous_to_impersonate: false
category:
count: 30
group:
count: 15
post:
include_images: false
max_likes_count: 10
post_revisions:
count: 50
tag:
count: 30
topic:
count: 30
replies:
# number of replies per topic between min and max
min: 0
max: 12
overrides:
# topic titles can be found in config/locales/faker.en.yml
# in the discourse_dev_assets gem
- title: "Coolest thing you have seen today"
count: 99
tags:
# number of tags per topic between min and max
min: 0
max: 3
user:
count: 30
email_logs:
count: 2
new_user:
username: new_user
email: new_user@example.com