Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

code-check/env-builder

Open more actions menu

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

297 Commits
297 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Circle CI

Code-Check test environment builder

This makes a virtual machine which has several programming languages.

Packages which installed by this.

  • java 8
  • node 0.12.x
    • nvm
    • npm
    • typescript
    • coffeescript
    • mocha
  • php 5.5
    • composer
  • ruby 2.2
  • scala 2.11.6
    • sbt 0.13.8
    • activator 1.3.2
  • python3
  • git 2.x
  • mysql 5.6

Prerequisite

  • VirtualBox
  • Vagrant 1.7 or later
  • Ansible

Add ubunt1404 to vagrant box

vagrant box add ubuntu1404 https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box

And then make your own Vagrantfile and hosts.
For vagrant, you have Vagrantfile.sample. Also , hosts-vagrant, and hosts-local are provided for hosts sample file. IP address setting for Vagrantfile.sample and hosts-vagrant are connected, so just running commands below would be an easiest way to start.

$ mv Vagrantfile{.sample,}
$ mv hosts{-vagrant,}

Export the private key path for GitHub and OS user name of guest PC.

export PRIVATE_KEY_PATH=~/.ssh/id_rsa
export OS_USER_NAME=vagrant

Make local environment

All roles are included in all.yml.
If you want to choose using roles, make your own yaml file.

git clone https://github.com/code-check/env-builder.git code-check-env
cd code-check-env
vagrant up
ansible-playbook all.yml

Run

vagrant ssh

Trouble shooting

Use vagrant 1.7 or later

The location of ssh private key was changed from 1.7.
Check existence of .vagrant/machines/default/virtualbox/private_key

Maintain ~/.ssh/known_hosts

If you destroyed the virtual machine and recreate it.
Its host signature changes.
So, you have to remove existing host signature(192.168.33.101) from known_hosts.

About

Test environment builder

Resources

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Morty Proxy This is a proxified and sanitized view of the page, visit original site.