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
{{ message }}
This repository has been archived by the owner on Jul 2, 2021. It is now read-only.
Instances in Elastic Beanstalk come and go. Any files stored on the instance will only survive until Beanstalk decides to replace the instance. Because of this, we need to store log files elsewhere.
Here are some options to look into:
Email the job report as soon as its done
Store the job report in the database
Store the job report as a file in Django Storage object, which needs to be moved to S3 or similar
The text was updated successfully, but these errors were encountered:
I split out the work for S3/Django Storage to another issue since that needs to happen regardless of this one. I think in the long term we want to store the job reports on s3 or in the database, but for the short term, emailing the report should be fine.
Another option would be to just log to the django logger, and then figure out how to pull the logs from Beanstalk which is something we should do anyway for debugging.
Instances in Elastic Beanstalk come and go. Any files stored on the instance will only survive until Beanstalk decides to replace the instance. Because of this, we need to store log files elsewhere.
Here are some options to look into:
The text was updated successfully, but these errors were encountered: