.travis | ||
app | ||
bootstrap | ||
config | ||
modules | ||
public | ||
resources | ||
storage | ||
tests | ||
.gitignore | ||
.htaccess | ||
.travis.yml | ||
artisan | ||
CODE_OF_CONDUCT.md | ||
composer.json | ||
composer.lock | ||
composer.phar | ||
env.php.example | ||
index.php | ||
LICENSE | ||
Makefile | ||
package-lock.json | ||
package.json | ||
phpunit.xml | ||
Procfile | ||
README.md | ||
webpack.mix.js |
phpvms 7
The next phpvms version built on the laravel framework. work in progress. If you're looking for the old, phpVMS classic, it's available here.
installation
A full distribution, with all of the composer dependencies, is available at this tarball link. It's currently updated with every commit
Composer Access
run the following commands. for right now, we're running on sqlite. for mysql, set
DB_CONNECTION
to mysql
in the env.php
file.
cp env.php.example env.php
composer install --no-interaction
php artisan database:create
php artisan migrate:refresh --seed
then point your webserver to the /public
folder.
development environment
For development, copy the included env.php.example
to env.php
file. By default, it uses sqlite
instead of mysql. This makes it much easier to be able to clear the database and new fixtures.
The easiest way to load locally is to install Laravel Valet (if you're running a Mac). Once you install it, go to your phpvms directory, and run:
cp env.php.example env.php
php artisan key:generate
make install # this will install everything
valet link phpvms
Now going to http://phpvms.dev should work. If you want to use mysql,
follow the valet directions on installing mysql (brew install mysql
) and then update the
env.php
file to point to the mysql.
The default username and password are "admin@phpvms.net" and "admin". To see the available users in the development environment, see this file
creating/resetting the environment
I use Makefiles to be able to quickly setup the environment.
# to do an initial setup of the composer deps and install the DB
make install
Then to reset the database/clear cache, use:
make reset
database seeding
There is a database/seeds/dev.yml
which contains the initial seed data that can be used
for testing. For production use, there is a prod.yml
file. The make reset
handles seeding
the database with the data from the dev.yml
.
updating
extract files and run the migrations:
php artisan migrate