My guess is that the job is divided into build and deploy to prevent deployment from starting when the django app is not fully compressed, and it seems to be used to store the build result. is this right?
Hi, this manually created s3 bucket servers as temporary file storage and allows EBL-cli to move build further to EBL environment. Beanstalk creates its own s3 bucket for storing application versions, and I guess we could use it too. But that isn't convinient when you use more than one environment. So I think of it as GitHub owned bucket.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
hi, i have a question.
I know that version elastic beanstalk is automatically managed through a zip file. Is there any reason to create and use an additional s3 bucket?
My guess is that the job is divided into build and deploy to prevent deployment from starting when the django app is not fully compressed, and it seems to be used to store the build result. is this right?
Hi, this manually created s3 bucket servers as temporary file storage and allows EBL-cli to move build further to EBL environment. Beanstalk creates its own s3 bucket for storing application versions, and I guess we could use it too. But that isn't convinient when you use more than one environment. So I think of it as GitHub owned bucket.