difference betwen dev & prod about adminthemebundle HOT 6 CLOSED

Hmm, the prod directory seems to be outdated here. See https://github.com/avanzu/AdminThemeBundle/tree/master/Resources/public/static

from adminthemebundle.

had the same issue
2 solutions :)

using capifon to deploy my app into production - copying dev assets to prod

invoke_command "sh -c 'cd #{latest_release}/web/bundles/avanzuadmintheme/static && cp -pva dev/* prod/'"

or after deploy generate the prod assets :) - seems cleaner to me, but requires uglifyjs und uglifycss installed.

invoke_command "sh -c 'cd #{latest_release} && app/console avanzu:admin:build-assets --env=prod'"

from adminthemebundle.

Thank you @hjanuschka ,
an other solution I've found is to fetch vendors and install assets using the --env prod option.

php app/console avanzu:admin:fetch-vendor --env prod

from adminthemebundle.

app/console avanzu:admin:fetch-vendor --env=proddidn't work for me :D

from adminthemebundle.

@hjanuschka thank for pointing this out :)
if you like this adminthemebundle, have a look on this boilerplate I've made to kickstart project in a minute ! https://github.com/numerogeek/ultimate-symfony2-boilerplate

from adminthemebundle.

After fetching the vendor scripts (which should be optional since 1.3.0) you will need to regenerate the static assets as described here. The upgrade notice is obviously not very clear about that.

from adminthemebundle.