CHEF PROVED TO BE AN UNRELYABLE TOOL AND WE'RE MOVING TO DOCKER, SEE OUR FIRST STEPS [HERE] (https://github.com/jtalks-org/jtalks-cicd).
If you want to start a brand new environment for JTalks with installed software using just a couple of commands - then this is what you're looking for. This project helps you to start a virtual environment using Vagrant + Chef scripts.
In order to start one of JTalks component, you need to go through several steps.
vagrant up
- this starts your env and runs Chef scripts. This may take a lot of time especially first time because it downloads software and virtual image from the internet.vagrant ssh
- log into the just created virtual machine. For Windows users you'll have to use Putty to log in via SSH. Use Host: localhost
, Port: 2222
. User: vagrant
, password: vagrant
.jtalks deploy --environment vagrant --project jcommune --build 2037
- this is just an example that start 2037th build of JCommune project.
jcommmune
you can specify poulpe
to start Poulpe.2037
you need to put a build you'd like to use, a list of them can be found in our Deployment Pipeline Repository. Every build has a suffix following major and minor version of the build.~/.jtalks
and can be changed if needed. For more information on how to install and use jtalks scripts see JTalks CICD projectjtalks-vm
folder.vagrant destroy
. After that you'll be able to start a brand new env again by running vagrant up
vagrant suspend
and to continue work with it: vagrant resume
The very same cookbooks could be used on usual servers that don't leverage virtualization. E.g. we use them in order to install software, see folder roles
. In order to install everything onto the machine, feel free to leverage install-chef script. After installation you can go to /var/chef/jtalks-vm
and install software using server roles, e.g.: sudo chef-solo -j roles/jtalks-servers.json
If you have problems, please contact us: project[at]jtalks[.]org