Is there any kind fellow windows user who had faced similar problems that can provide me some concrete ways in setting up the APE?
From their homepage: http://www.ape-project.org/wiki/index.php/Setup
Also from their google group: http://groups.google.com/group/ape-project/web/installing-ape-on-ubuntu-9-04
The second is specific to ubuntu 9.04 so fi you are using virtual box you could install ubuntu 9.04 and go through this guide.
Related
I am wondering If we can use a different distro in Laravel Homestead. Right now it is preconfigured to use an Ubuntu Distro. Can we use other distro like fedora, arch etc?
Short Answer: No because it's not a simple matter.
Long Answer: I'm working on it, it's just slow going. In my day job I've always used RHEL or CentOS so I've always wanted a CentOS flavored version of Homestead. That's exactly what I've started building with EnterpriseHomestead and EnterpriseSettler projects. It's not quite ready for a alpha, but it is close (despite I haven't had much time to work on it lately, Homestead and support keeps my OSS time pretty tied up)
If you'd like to help out please jump into the repo and start testing / asking questions. I also have #enterprisehomestead on the Freenode IRC network.
When trying to init a Vagrant box with VirtualBox, I keep getting this error:
No usable default provider could be found for your system.
Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.
The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.
If you believe you already have a provider available, make sure it is
properly installed and configured. You can see more details about why
a particular provider isn't working by forcing usage with vagrant up
--provider=PROVIDER, which should give you a more specific error message for that particular provider.
After some searching it seems that Vagrant has compability issues with particular versions of VirtualBox. I'm running Vagrant 2.0 together with VirtualBox 5.2 on MacOS High Sierra. Is this simply not possible, or is there a workaround?
Update: It is a compatibility issue between Vagrant and VirtualBox – tried installing VirtualBox 5.1.14 instead and it works with Vagrant 2.0.
You can also use it with VirtualBox 5.2 with this patch:
https://gist.github.com/roktas/ec34960d2e5d74c3cc4f35bc78bc676d
I just started learning Vagrant and succeeded in using it. I went through this vagrantbox.es where we "download" the "templates".
I have some doubts and would be great if anyone can explain me:
1) Vagrant --> My understanding is t hat it helps in automating installing the Virtual machines in Virtualization software like Virtualbox. Is this correct?
2) Now, as per the instructions that I followed in one of the video tutorials, we need to 'download' the VM, from this link.
My doubt is what are we downloading from the link in point #2? Using Vagrant, are we downloading a VM (and which gets installed into Virtualbox, for example?). Can't we use any .iso image and let vagrant install it? I am bit confused here.
Can anyone who has used vagrant explain what exactly are we downloading?
2) Now, as per the instructions that I followed in one of the video tutorials, we need to 'download' the VM, from this link.
Must be a bit dated tutorials, even though it is still a good reference, nowadays people will download boxes from https://atlas.hashicorp.com/boxes/search. The platform is officially supported by hashicorp but everyone can upload boxes into the platform, and you can directly reference boxes from atlas such as ubuntu/trusty64 in your vagrantfile and vagrant will know how to download the box and install it for you so it saves you some steps.
My doubt is what are we downloading from the link in point #2? Using Vagrant, are we downloading a VM (and which gets installed into Virtualbox, for example?). Can't we use any .iso image and let vagrant install it? I am bit confused here.
There are some 'official' box supported by hashicorp. Some organization like laravel pushes their own official boxes (like laravel/homestead and they support virtual box and vmware provider). It will be up to you to review the box you reference and make sure about its source.
you can create your own box from the OS iso using tool such as packer you will find plenty of available packer templates on github to create boxes for different OS flavors
And finally, are these images "full" OS plus the tools (e.g. tomcat, php as you described)
This will depend - in the case of Laravel they would provide a box with OS + the stack but generally the boxes are minimal (and you want to keep it this way). You will provision this using a tool of your choice (shell, ansible, puppet ...)
Trying to solve my problem I did the next:
Added 'Ubuntu_64' to config file.
Switched my WiFi off (saw this solution at Laravel forums) before 'vagrant up' execution.
Enabled GUI.
Rolled the VirtualBox and its extension back (also from Laravel forums).
The VMs which were successfully run with Vagrant are the Debian Wheezy 7.5 x32 built with puphpet and precise32.
As we can see, only x32 VMs could be run on my machine. I don't know why.
Here is my machine info:
OS: Ubuntu 12.04 64
Processor: AMD A8-4500M, 2 cores
Virtualization is enabled in BIOS. See screenshot similar to my BIOS view: screenshot
The latest Vagrant, VirtualBox and VirtualBox Extensions pack are installed
my user is added to virtualbox group
Thanks in advance.
Dude, your question helped me to fix my problem!
I was getting this connection timeout, turned my wifi off and bam! All working fine!
Double check if your ubuntu is really 64 bit.
I got some problems with some linux architectures for AMD in the pest!
There are a few and sometimes they can be a headache.. I think I got this problem with centos, it was i686 instead of simple x64. I don't really know the difference but what you can try doing is:
Instead of adding the homestead box (vagrant box add laravel/homestead)
Why dont you try adding a simple ubuntu-32 machine and then you run vagrant up.
I dont really know if it's going to work, but it's worth trying!
Thanks again for your answer, it really helped me
I've been experiencing a problem with Virtualbox on my Fedora 13.
When I try to setup virtual machine instance with Windows it just hangs the system with no reaction on keyboard commands with no respond to anything except physical halting. Please help what might be the problem?
Sultan
which version of the virtualbox are you using, is the latest. Also you could try to re-install the software it may help you. One thing that usually helps is to delete the disk image file that you create for the image or use a different iso file to install your windows iamge.
Try one of those solutions, can't say what is the specific problem with your description
regards