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 }}
Repository navigation
Angular CLI installation fails on Ubuntu under Vagrant with killed #1192
changed the title [-]Angular CLI installation fails on Ubuntu with killed[/-][+]Angular CLI installation fails on Ubuntu und Vagrant with killed[/+]on Jun 24, 2016
changed the title [-]Angular CLI installation fails on Ubuntu und Vagrant with killed[/-][+]Angular CLI installation fails on Ubuntu under Vagrant with killed[/+]on Jun 24, 2016
@manuelfink do you have any advice on how to work with angular-cli deployment on AWS or other cloud instances where memory is limited? I would like to adhere to the structure of src / dist and having the app built from src when deploying to prod.
Is there a simple way to manage this with angular-cli or will I have to go back to a custom build process with something like gulp?
Activity
[-]Angular CLI installation fails on Ubuntu with killed[/-][+]Angular CLI installation fails on Ubuntu und Vagrant with killed[/+][-]Angular CLI installation fails on Ubuntu und Vagrant with killed[/-][+]Angular CLI installation fails on Ubuntu under Vagrant with killed[/+]manuelfink commentedon Jun 24, 2016
Problem is caused by too less memory. Installation needs at least 1GB ram
trickpattyFH20 commentedon Jul 31, 2016
@manuelfink do you have any advice on how to work with angular-cli deployment on AWS or other cloud instances where memory is limited? I would like to adhere to the structure of src / dist and having the app built from src when deploying to prod.
Is there a simple way to manage this with angular-cli or will I have to go back to a custom build process with something like gulp?
khaidinh commentedon Apr 28, 2017
@trickpattyFH20 You can add some swap on your constrained instances. I posted some links on #2630 if you still need it.
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.