alumni_lookup

YAML Runtime vs Seed Import Guide

Use this guide when editing YAML in config/ or db/seeds/.

Quick Matrix

File	How It Is Used	Edit Effect	What You Must Do
config/welcome_packs.yml	Loaded into Cp::WelcomeContentGenerator::PACKS	Not re-imported to DB; templates are app runtime config	Restart app processes to reload YAML. Regenerate welcome content where needed.
config/faq.yml	Read by Cp::HelpController + config_for(:faq) (tooltips)	Runtime config change	No seed import. Changes are picked up by app reads.
config/career_resources.yml	Read by Cp::CareersController	Runtime config change	No seed import. Changes are picked up by app reads.
config/primary_contacts.yml	Read at boot (config/initializers/primary_contacts.rb) and via config_for(:primary_contacts)	Hybrid: some paths are boot-loaded, some runtime	No seed import. Restart app to ensure all paths see latest values.
db/seeds/role_ideas.yml	Imported by bin/rake role_ideas:seed	No runtime effect until import	Run bin/rake role_ideas:seed after edits.

Important Notes

config/welcome_packs.yml

• Edits do not automatically rewrite existing Cp::Community#welcome_content.
• The file controls template generation, not a background DB sync.
• Use bin/rake welcome_content:generate[...] or bin/rake welcome_content:generate_all CONFIRM=1 if you need to apply new copy to communities.

db/seeds/role_ideas.yml

• bin/rake role_ideas:seed is additive/idempotent.
• It skips rows that already exist with the same body + role + target.
• If you change existing idea text, review resulting records (you may need manual cleanup or admin edits for older rows).

Rails-Managed YAML in config/

These are framework config files, not seed imports:

• config/database.yml
• config/storage.yml
• config/cable.yml
• config/locales/en.yml
• config/locales/devise.en.yml

For these files, you do not run a seed import task. Use normal app deploy/restart/reload practices for your environment.