You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a Neos application running in AWS ECS and different containers makes it more difficult to track the location of the exception dumps (which could be useful in production to debug certain problem). One idea to solve that would be to have an implementation of ThrowableStorageInterface that is able to store the exception dumps in a S3 bucket (as opposed to Data/Logs/Exception FileStorage).
Maybe this is out of scope of this extension but it would fit the configuration that is already present here (credentials etc), so it might be useful to have the functionality in place here at first.
The text was updated successfully, but these errors were encountered:
Idea for a new feature:
Having a Neos application running in AWS ECS and different containers makes it more difficult to track the location of the exception dumps (which could be useful in production to debug certain problem). One idea to solve that would be to have an implementation of
ThrowableStorageInterface
that is able to store the exception dumps in a S3 bucket (as opposed toData/Logs/Exception
FileStorage).Maybe this is out of scope of this extension but it would fit the configuration that is already present here (credentials etc), so it might be useful to have the functionality in place here at first.
The text was updated successfully, but these errors were encountered: