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.

Sign up for GitHub

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

fix typo and remove $ so gitclip works #1544

Merged
merged 1 commit into from
Jan 2, 2024
Merged

fix typo and remove $ so gitclip works #1544

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions Resources/doc/optimizations/resolve-cache-images-in-background.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ the result. Then it redirects the client to the generated image file.

This works without any further tooling. There are some important disadvantages however:

* Applying all the filters to an images can take a lot of time and memory;
* Applying all the filters to an image can take a lot of time and memory;
* The images have to be processed by the web server answering web requests. This increases the load
on the server and may affect performance;
* The resolve controller URL is different from the cached image URL. When the image needs to be
Expand All @@ -33,7 +33,7 @@ First, `install symfony/messenger`_ with composer:

.. code-block:: terminal

$ composer require symfony/messenger
composer require symfony/messenger

.. code-block:: yaml

Expand Down Expand Up @@ -70,7 +70,7 @@ We need to run at least one consumer for the messages:

.. code-block:: terminal

$ php bin/console messenger:consume liip_imagine --time-limit=3600 --memory-limit=256M
php bin/console messenger:consume liip_imagine --time-limit=3600 --memory-limit=256M

You can run the consumers on a separate machine, as long as it shares the same storage for the
cached images. In a cloud system, you could even scale consumers based on the queue size to get
Expand Down Expand Up @@ -156,7 +156,7 @@ Here's how you can run it:

.. code-block:: bash

$ ./bin/console enqueue:consume --setup-broker -vvv
./bin/console enqueue:consume --setup-broker -vvv

Step 4: Send resolve cache message
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down
Loading