Skip to content

[Deployment] Updated building assets in favor of Encore over Assetic #10238

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

Merged
merged 4 commits into from
Sep 4, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 2 additions & 11 deletions deployment.rst
Original file line number Diff line number Diff line change
Expand Up @@ -177,25 +177,16 @@ Make sure you clear and warm-up your Symfony cache:

$ php bin/console cache:clear --env=prod --no-debug

E) Dump your Assetic Assets
~~~~~~~~~~~~~~~~~~~~~~~~~~~

If you're using Assetic, you'll also want to dump your assets:

.. code-block:: terminal

$ php bin/console assetic:dump --env=prod --no-debug

F) Other Things!
E) Other Things!
~~~~~~~~~~~~~~~~

There may be lots of other things that you need to do, depending on your
setup:

* Running any database migrations
* Clearing your APC cache
* Running ``assets:install`` (already taken care of in ``composer install``)
* Add/edit CRON jobs
* ref:`Building and minifying your assets <how-do-i-deploy-my-encore-assets>` with Webpack Encore
* Pushing assets to a CDN
* ...

Expand Down
2 changes: 2 additions & 0 deletions frontend/encore/faq.rst
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
FAQ and Common Issues
=====================

.. _how-do-i-deploy-my-encore-assets:

How do I deploy my Encore Assets?
---------------------------------

Expand Down