| Vagrant.configure(2) do |config| | |
| config.vm.box = "centos/7" | |
| config.vm.network "private_network", ip: "192.168.55.20" | |
| config.vm.synced_folder ".", "/home/vagrant/dev", nfs: true | |
| config.vm.provider "virtualbox" do |v| | |
| v.name = "golangvbox" | |
| end | |
| config.vm.provision "shell", path: "provision.sh", privileged: true, binary: false |
To 'clone' a container, you'll have to make an image of that container first, you can do so by "committing" the container. Docker will (by default) pause all processes running in the container during commit to preserve data-consistency.
For example;
docker commit --message="Snapshot of my container" my_container my_container_snapshot:yymmdd
| /** | |
| * Basic example to pass values between parent and child components in React | |
| * Seems to be in line with this | |
| * http://stackoverflow.com/questions/24147331/react-the-right-way-to-pass-form-element-state-to-sibling-parent-elements | |
| * Now I have the state in parent and child. Is that good or bad? Why would I need it in child? | |
| * Could probably take that out | |
| * */ | |
| class Parent extends React.Component { | |
| constructor(props) { | |
| super(props); |
Operator Mono w/ Italics on OSX Vim
| image: nikolaik/python-nodejs:latest | |
| stages: | |
| - install | |
| - test | |
| - deploy | |
| prodInstall: | |
| stage: install | |
| script: |