I have tested installing posty through vagrant . So following are the issues i've faced and i fixed those problems .. so we need to make these changes in our vagarant script
After entering vagrant up . its was run successful .. at some point i got following error
==> default: /usr/local/lib/ruby/gems/2.0.0/gems/bundler-1.9.4/lib/bundler/runtime.rb:34:in `block in setup'
==> default: :
==> default: You have already activated rack 1.6.0, but your Gemfile requires rack 1.5.2. Prepending `bundle exec` to your command may solve this.
then i logged in to vm.. i have fixed the error with following commands
Again it was failed at installing apache2 passenger module with following error
==> default: mkdir -p buildout/support-binaries
==> default: virtual memory exhausted: Cannot allocate memory
==> default: rake aborted!
==> default: Tasks: TOP => apache2 => buildout/support-binaries/PassengerAgent => buildout/support-binaries/ServerMain.o
==> default: (See full trace by running task with --trace)
==> default: ---- End output of passenger-install-apache2-module --auto --languages ruby ----
This is becuase of most of system virtual memory may exhaust depending on the system configuration. passanger modules requires more virtual memory.. so its bettern if we have atleast swap disk which will bypass the problem. so we need to run the following commands to avoid this error
Hi @chicobico @lweis
I have tested installing posty through vagrant . So following are the issues i've faced and i fixed those problems .. so we need to make these changes in our vagarant script
After entering
vagrant up
. its was run successful .. at some point i got following errorthen i logged in to vm.. i have fixed the error with following commands
Again it was failed at installing apache2 passenger module with following error
This is becuase of most of system virtual memory may exhaust depending on the system configuration. passanger modules requires more virtual memory.. so its bettern if we have atleast swap disk which will bypass the problem. so we need to run the following commands to avoid this error
I am requesting you to please make appropriate changes in the vagrant script and make it live