thirty bees vagrant LEMP stack in progress on GitHub
I’m creating a thirty bees vagrant lemp stack based on trusty64/ubuntu server 17.04 with the following:
- mariadb [ latest stable release ]
- Redis / php-redis cache
- puppet master [ build vm infrastructure ]
After the github project is table, I’ll post to atlast.hashicorp.com for download in your local vagrant installation. In the meantime, hop on if you’re comfy with any of those technologies and fork/pull request and contribute? https://github.com/denverprophitjr/thirty-bees-vagrant
If we can get thirty bees into a phar archive, I can modify a new puppet module to install thirty bees automatically and inside the virtual machine. The feature request is at https://thirtybees.com/suggestions/create-thirty-bees-phar-for-automated-builds-in-puppet-vagrant/
Nice project, but I’m not sure if a PHAR is necessary. A decent provisioning script would be a good start already. I’m keeping an eye on your project!
I think that even a Puppet script isn’t necessary. Have a look at my script to create an ElasticSearch instance: https://github.com/thirtybees/elasticsearchvagrant
A shell script is all it needs.
You could also use git to download thirty bees. This will make it a lot easier to make the version number configurable in the
@mdekker could the release be called stable.tgz? You think that’s better than guessing which tag release to edit in the Vagrantfile?
What do you mean?
when you make a release and call it stable.tgz instead of having to edit
Vagrantfilewith the git branch to export.