ElkArte Community

Project Support => General ElkArte discussions => Topic started by: Ant59 on July 12, 2015, 07:26:56 am

Title: Elkarte Vagrant Environment
Post by: Ant59 on July 12, 2015, 07:26:56 am
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.
Title: Re: Elkarte Vagrant Environment
Post by: Spuds on July 12, 2015, 09:07:31 am
awesome, thanks for sharing !
Title: Re: Elkarte Vagrant Environment
Post by: emanuele on July 12, 2015, 05:07:21 pm
What Spuds said! :D
Title: Re: Elkarte Vagrant Environment
Post by: Joshua Dickerson on July 12, 2015, 06:47:25 pm
@ant59 have you heard of PuPHPet (https://puphpet.com/)?
Title: Re: Elkarte Vagrant Environment
Post by: Ant59 on July 14, 2015, 05:53:45 am

I've seen it, but never used it. Is it just another provisioning manager like Puppet or Chef?
Title: Re: Elkarte Vagrant Environment
Post by: Joshua Dickerson on July 14, 2015, 02:12:24 pm
It is a GUI to create a provisioning script which uses Puppet. Take a look. Makes life easier.
Title: Re: Elkarte Vagrant Environment
Post by: Joshua Dickerson on July 14, 2015, 04:55:56 pm
Do you use Netbeans or PHPStorm?
Title: Re: Elkarte Vagrant Environment
Post by: Ant59 on July 14, 2015, 06:42:15 pm
I'll take a look but I like the shell script  :)

I use vim.
Title: Re: Elkarte Vagrant Environment
Post by: Ant59 on July 24, 2015, 08:14:37 am
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.