{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 欢心 的问题《Keep certain existing files when deploying to Elas》','https://www.manongdao.com/q-1279216.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
We have SOLR in our app directory on EC2 server and not on our local git repository. When we are pushing our local repository to EC2, it is erasing the Solr directory. We have put the directory name in our .gitignore file, but it still overwrites the SOLR directory.
How do we prevent overwriting certain files that are only on the EC2 server (in the var/app/current directory)?
AWS Elastic Beanstalk instances do not have persistent storage. EC2 instance is restored with default filesystem on each git push.
You can persist SOLR files in S3 and automatically retrieve them on container startup with container commands.
Other options are mentioned in "Persistent Storage" section in AWS Elastic Beanstalk Design Considerations.