As I mentioned in my last post, Meat comes packaged as an OVA to easily deploy into VMware environments. The quickest path for testing for me was to install in VMware Workstation; simply click File >> Open and select the OVA. By default, it connects in bridged mode (e.g. on your network) however I run my lab behind the Workstation NAT so I made that change. Connect appropriately for your environment. Before you begin, add another virtual drive with at least 10GB of space.
Once the VM is powered on you should be prompted to connect to the IP address it received during boot via DHCP, or you have the option to configure networking via the console; both options shown here. Again, this will depend on your environment.
When you navigate to the IP and port, in the case of Meat 8080, you’ll be taken to the first step in the setup wizard.
Start the installation, and accept the agreement. If you forgot to add additional space you will now be prompted to do so. Upload your license and the installation will begin.
Once done, you will be prompted to configure your workspace. In a workspace you can have a collection of different projects and users, permissions, groups and see activity feeds. For example, here is a workspace I created.
As I would in GitHub, I can see the URLs to access the repository in my Git client via either HTTPS or SSH
I can also import from existing popular repositories such as Git, GitHub, or BitBucket which is useful for testing Meat out as you can bring your projects in that already exist.
For example, here is my Ansible-Test-Playbooks repository from GitHub, imported into Meat. All I had to do was authorize Meat, and select the repository I wanted to import. It also supports readme files as you would be accustomed to in GitHub.
Not only did it import the repository, but a history of my commits as well!
As I mentioned in my previous post, I can edit files directly in Meat, and as I had hoped prompts me to commit those changes versus just by passing the typical commit/push process those who use GitHub are familiar with. To boot, Meat automatically made notes of my changes, versus having to enter them in vim and then saving them before doing a git push.
You may also notice the reply box, this is a social aspect of Meat I hadn’t mentioned. You can see a list of comments, adds, deletes, changes all from the activity stream as well. Here is my commit done via the Meat UI with a comment in the stream.
That’s it for today, next I will be looking into Releases which is the ability to deploy code to servers directly from Meat.