Vagrant, VirtualBox built-in or no? - virtualbox

Trying to get set up with Vagrant but getting the error:
The "VBoxManage" command or one of its dependencies could not be found.
Please verify VirtualBox is properly installed. You can verify everything
is okay by running "VBoxManage --version" and verifying that the VirtualBox
version is outputted.
Just confused because the Vagrant documentation states:
"The getting started guide will use Vagrant with VirtualBox, since it is free, available on every major platform, and built-in to Vagrant."
Don't want to install VirtualBox separately if its supposed to be included when I installed Vagrant. Running OSX 10.8 if it's relevant, guessing I just need to install VirtualBox? If that's the case, what do they mean in the documentation when they say it's "built-in"?

Installing VirtualBox is required if you plan on using VirtualBox with Vagrant. I'm guessing they meant that the VirtualBox integration is built-in?
Recently, they've abstracted out the VirtualBox specific code and are working on allowing for multiple providers. I believe VMWare is now supported in addition to VirtualBox.

I had this message but my problem was different. I use Vmware_fusion as the provider. Vagrant was not able to detect what provider I am using.It assumed that I am using VirtualBox. Had this issue fixed by calling vagrant up provider flag. Here is the full command
vagrant up --provider vmware_fusion

Related

deploying to ubuntu instance on aws from windows

I want to deploy a python project to ubuntu instance on aws from a windows operating system, but all tutorials I have encountered either use ubuntu or mac as their development/local machine.
Is the deployment from windows the same i.e. after createing the instance all I would then be doing from the local windows system would be running inside the ubuntu instance?
is there any tutorial which can help me achieve my objective?
Note i am deploying directly without git.
ANy help would be appreciated
To transfer files to an ubuntu instance you could use SSH, from windows you could download an SSH client such as Mobaxterm (https://mobaxterm.mobatek.net/)! or download Windows Subsystem for Linux (https://learn.microsoft.com/en-us/windows/wsl/install-win10)! then use SCP to copy files (https://www.computerhope.com/unix/scp.htm)!. Both options require that you have the .pem security file for your instance
Your best bet is going to be installing WSL(Windows Subsystem for Linux) and using that to run bash commands. This will make your life a whole lot easier as you won't have to look for Windows specific tutorials and you can now follow Ubuntu/Linux tutorials.
What is WSL? It is essentially a Linux VM built into Windows. It will provide you with a terminal running Ubuntu or pretty much any other Linux distro you could want.
How to install WSL

Node.JS native addons on LINUX [duplicate]

I'm using AWS Lambda, which involves creating an archive of my node.js script, including the node_modules folder and uploading that to their infrastructure to run.
This works fine, except when it comes to node modules with native bindings (using node-gyp). Because the binding was complied and project archived on my local computer (OS X), it is not compatible with AWS's (Amazon Linux) servers.
How can I cross-compile/install a node module (specifically, node-sqlite3) so when I upload it to another server arch it runs?
While not really a solution to your problem, a very easy workaround could be to simply compile the native addons on a Linux machine.
For your particular situation, I would use Vagrant. Vagrant can create virtual machines and configure them within seconds.
Find an OS image that resembles Amazon's Linux distro (Fedora, CentOS, others that use yum as package manager - see Wiki)
Use a simple configuration script that, when run by Vagrant on machine startup, will run npm install (optionally it might also remove the node_modules folder before to ensure a clean installation)
For extra comfort, the script can also create the zip file for deployment
Once the installation finishes, the script will shutdown the VM to avoid unnecessary consumption of system resources
Deploy!
It might require some tuning if the linked libraries are not at the same place on the target machine but generally this seems to me like the best and quickest solution.
While installing the app using Vagrant might be sufficient in some cases, I have found it necessary to build the app on Linux which is as close to Lambda's Amazon Linux AMI as possible.
You can read the original answer here: https://stackoverflow.com/a/34019739/303184
Steps to make it work:
Spawn new EC2 instance. Make sure it is based on exactly the same image as your AWS Lambda runtime. You can review Lambda env details here: http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html. In our case, it was Amazon Linux AMI called amzn-ami-hvm-2015.03.0.x86_64-gp2.
Install nvm and use it to install the same version of Node.js as on the AWS Lambda. At the time of writing this, it was v0.10.36. You can refer to http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html again to find out.
You will probably need to install git & g++ compiler on the EC2. You can do this running
sudo yum install git gcc-c++
Finally, clone your app to your new EC2 and install your app's dependecies:
nvm use 0.10.36
npm install --production
You can then easily download the node_modules using scp or such.
Same lines as Robert's answer, when I had to work on my MAC in a different OS I use vm ware like Oracle's free virtualizer VirtualBox to get a linux on my mac, no cost to me. Or sign up for a new AWS account, you get a micro for a year free. Use that to get your linux box, do whatever you need there.
AWS has a page describing how to deal with native NPM modules: https://aws.amazon.com/blogs/compute/nodejs-packages-in-lambda/

copy paste and cut text from host to guest in vmware workstation 15 player

I googled before and found that by turning on the "Enable copy and paste" under Guest Isolation, I can copy/cut/paste text from guest to host and vice versa. But I don't see "Guest Isolation" after clicking on Player->Manage->virtual machine settings->option. I have tried to install the VMware tools and I seem to have successfully installed it, but still no use. Is this feature only available in VMware pro?
For Ubuntu (Guest OS), you need to install open-vm-tools and open-vm-tools-desktop.
sudo apt install open-vm-tools open-vm-tools-desktop
Some versions of vmware-tools are buggy (copy&paste does not work). Try an older version (they can be downloaded for free from vmware.com).
Note that newer Linux distributions already include the vmware-tools. They may not be installed by default (see this answer).

Is there any well documented Redmine installation process

is there any well documented step by step procedure to install redmine?. I tried to install it on my Ubuntu machine.But i am unable to access it from another machine. please tell me how to it. is there any document which show how to host as centralized
See this guide: http://www.redmine.org/projects/redmine/wiki/redmineinstall. Its a general installation guide. I used it to install Redmine on Debian Jessie.

How can I downgrade CentOS 6.5 to CentOS 6.3 on VirtualBox 4.3.10

I ran the yum on CentOS 6.3, so that it turned into another kernel CentOS 6.5. After restart of the VirtualBox I couldn't anymore run neither the old nor the new OS. Do you know a way to downgrade to CentOS 6.3? How can I get into the machine with SSH without knowing it's IP address?
As for your second question, you require a DNS service and maybe you have it; you can check the settings of your DHCP server where list the hostname of your virtual machine. Assuming that you are in a scenario where you have a DHCP and DNS server normally called "Modem Router" and do require SSH Connection temporarily.
Now the first question, I have a lot to say, but to my knowledge, it is difficult to make a "downgrade" on linux on all packages that could be updated, if it is only the kernel and it is another matter. I suggest:
https://www.centos.org/docs/2/rhl-cg-en-7.2/buildkernel-bootloader.html