User tests: Successful: Unsuccessful:
The purpose is to create an "instant" virtual operating system including an AMP stack.
So you basically have to issue only one line on the CLI to get a working instance of the JTracker project for local development.
cd to/the/path where you downloaded/checked out the codevagrant up - NOTE: The very first startup will probably take some minutes to complete, since packages have to be downloaded. Time depends, as always, on you ISP.You have to run the setup from the command line of your virtual "guest" operating system.
cd to/the/path where you downloaded/checked out the codevagrant ssh - Welcome to Linux ;)cd /vagrant - ! Note that this is actually the repository root outside of your virtual machine which is mounted as a shared folder !! (!)./cli/tracker.php installconfig.vagrant.json will be used for setup.Go for the code
When you are finished and want to stop the VM to work with it later, you should either run halt or suspend, the latter requiring a bit more disc space while providing a somewhat faster startup.
vagrant halt OR vagrant suspendTo delete the whole VM run
vagrant destroyThe TrackerApplication has been modified to look for an environment variable JTRACKER_ENVIRONMENT.
If it is set to "something", a config file with the same name will be loaded.
Example
You may set the environment variable from inside a VirtualHost directive in one of your Apache config files.
<VirtualHost *:80>
...
SetEnv JTRACKER_ENVIRONMENT foobar
...
</VirtualHost>
With the environment variable set to foobar you will have to create the file config.foobar.json.
NOTE that you'll have to supply the environment variable separately to the CLI application - depending on your OS:
Note: Apache and PHP are configured to write log files to the logs directory at the repo root outside the virtual machine. They are at "debug" level, so they are growing fast. Consider logrotate or similar.
P.S.: You might also like: elkuku/vagrant-joomla-cms
Now this looks interesting.