Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

209587Update to use seeds.d and plugin assets. #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ehelms
Copy link
Member

@ehelms ehelms commented Jun 17, 2015

Foreman supports loading seeds from db/seeds.d and thus being able to
define individual seeds and control the ordering similar to how Foreman
core does. Plugin assets needs only be defined in the settings, and
the plugin assets rake task will handle compiling the plugin assets
properly.

Foreman supports loading seeds from db/seeds.d and thus being able to
define individual seeds and control the ordering similar to how Foreman
core does. Plugin assets needs only be defined in the settings, and
the plugin assets rake task will handle compiling the plugin assets
properly.
end
end
initializer 'foreman_plugin_template.assets.precompile' do |app|
app.config.assets.precompile += assets_to_precompile

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought this was required if you were using rake assets:precompile to recompile the whole application. SETTINGS is enough if you're just using the plugin-specific asset precompilation, but for say, a source install with plugins then they'd do everything.

@ekohl
Copy link
Member

ekohl commented Nov 25, 2022

@ehelms amazingly this still applies without conflicts, but is it actually still needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants