- Notifications
You must be signed in to change notification settings - Fork5
dockito/devbox
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
- Start by cloning this repository inside a
Development
folder where you keep all your projects; - Then go inside this new folder:
cd Development\devbox
; - Start the vagrant box:
vagrant up
; - Log in into your new box:
vagrant ssh
.
It will sync its parent folder (Development
), making all your projects available inside the VM at the/vagrant
folder.
You will have aCoreOS install withCompose (former Fig) and anHTTP Proxy.
https://coreos.com/docs/cluster-management/scaling/adding-disk-space/
In case occur some weird problem in the first vagrant up the following steps have usually solved the it:
# runs the provision manuallyvagrant provision# reloads the vm againvagrant reload
Since each developer has their own preferences for what should be automatically configured in the VM (e.g. initial access folder and custom alias). Including acustom-provision.sh inside devbox directory it will be provisioned by Vagrant.
Basic example:
# bash_profile on CoreOS is read-only on file system# due that we clone the original one and uses this new copyunlink /home/core/.bash_profilecp /usr/share/skel/.bash_profile /home/core/.bash_profile# configures bash profile to access the vagrant folder# after log into the vm through sshecho"cd /vagrant/bravi">> /home/core/.bash_profile
About
vagrant box with Docker, Docker Compose and Nginx
Resources
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
No releases published
Packages0
No packages published