Skip to main content
Topic: Elkarte Vagrant Environment (Read 1590 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Elkarte Vagrant Environment

Just threw together a Vagrant environment for working on Elkarte's source. Clone my repo, then clone the Elkarte repo inside it and "vagrant up". It will pre-populate the database, copy a basic Settings.php, and sync the sources/ folder (you can sync more by adding them to the Vagrant file and adding an "exclude=" flag to the rsync command in the provisioning script).

This gives an environment that leaves the Elkarte Git repo untouched by the running Elkarte instance, but which gives instant results for changes to scripts in the sources/ directory.

https://github.com/Ant59/elkarte-vagrant

Hope it's useful to someone.

Re: Elkarte Vagrant Environment

Reply #1
awesome, thanks for sharing !
Squish squish. squish, squish, squish.
Find a bug,
Make a wish.

Re: Elkarte Vagrant Environment

Reply #2
What Spuds said! :D
Bugs creator.
Features destroyer.
Template killer.

Re: Elkarte Vagrant Environment

Reply #3
@ant59 have you heard of PuPHPet?
I am currently doing freelance work. If you need coding help, forum help, or server maintenance, shoot me a PM and let me know.


Re: Elkarte Vagrant Environment

Reply #5
It is a GUI to create a provisioning script which uses Puppet. Take a look. Makes life easier.
I am currently doing freelance work. If you need coding help, forum help, or server maintenance, shoot me a PM and let me know.

Re: Elkarte Vagrant Environment

Reply #6
Do you use Netbeans or PHPStorm?
I am currently doing freelance work. If you need coding help, forum help, or server maintenance, shoot me a PM and let me know.

Re: Elkarte Vagrant Environment

Reply #7
I'll take a look but I like the shell script  :)

I use vim.

Re: Elkarte Vagrant Environment

Reply #8
I've updated the repo to exclude the sources directory in setting permissions during provisioning (else Git thinks the files have changed). Also added a php.ini to the provisioning so that display_errors is always on in the Vagrant development environment.