-
Notifications
You must be signed in to change notification settings - Fork 1
1. Installation Instructions
- Install Laragon WAMP
- Run PHPStorm / IDEA and create a new project from Github in your laragon's documents root folder. (Typically located in
{path to laragon}/www/
) - Laragon should now list your new project. Open the control panel and hit start all.
- Open Laragon and click Terminal, navigate to your project root and type
composer install
- Run
yarn
once and follow it up withyarn install
You can continue setting up while it fetches all our dependencies for you.
Since you're pulling this repo, laragon's automagic setup will be be slightly wrong. To fix it :
- Open Laragon's Menu
- Navigate to Apache > sites-enabled > auto.soen341.oo.conf
- If it's not already there, append
public/
to every instance of the directory path, i.e when you seen.../SOEN341/<add here>
- You may need to restart the apache service for things to update.
Pretty straight forward but nothing will work unless you do this.
- Copy the .env.example file and call it .env
- run
php artisan key:generate
- you can also do this from within PHPStorm
Again, you're pulling a repo so laragon won't automatically create a database for you. Lets do it manually :
- Open HeidiSQL from laragon's menu
- Login with root and your password (empty by default)
- Create a new database and name it SOEN341 (you can leave the collation as is but utf8 is preferred)
- Switch to a terminal and run
php artisan migrate
in your project root
Obviously you need PHPStorm, you can get it for free here --> thanks uni
PHPStorm helps you as much as it can but it needs to know what it's reading for auto-complete to work.
The base PHPStorm install comes with apparently everything except these plugins :
- Laravel Plugin
- LaravelStorm
To install them : open Settings (CTRL + ALT + S) > Plugins > Click browse repositories, search for each then install.
- Open File > Settings (CTRL + ALT + S) -> Languages & Frameworks > PHP
- Change language level to appropriate version. (We're using 7.2)
- Click the
...
next to CLI interpreter and hit the + to add a new one, name it as you wish. - The path to the php executable is as follows
{LARAGON_INSTALL}\bin\php\{some_php_version_here}\php.exe
- Optional but recommended debugger step
- Back in the 1st window you should go into the PHP Runtime tab and hit Sync Extensions with Interpreter.
Not really required but will make your life VERY easy
- Open Settings (CTRL + ALT + S) -> Tools > Terminal
- Change Shell path to
{path to laragon goes here}\bin\cmder\cmder.bat
PS: Basically saves you the trouble of adding everything to the PATH variable on your machine. All the commands just work, no questions.
Not really required but you'll be updating dependencies so why not make it safe, almost automatic and easy as hell
- Open Settings (CTRL + ALT + S) -> Languages & Frameworks > PHP > Composer (Install from plugins if you don't have it for some reason)
- Path to json should be
{path to project root}\composer.json
- For the execution choose executable, add the following path
{path to laragon}\bin\composer\composer.bat
and use default interpreter. (Alternatively choose phar and use the .phar)
Really not required buuuut will make my life slightly easier... no? okay. fine don't make my life easy.
- Open Settings (CTRL + ALT + S) -> Languages & Frameworks > Node.js & NPM
- Add a new node interpreter
- Path to the executable is as follows
{path to laragon}\bin\nodejs\{some_node_version_here}\node.exe
Not required unless you want to handle DB things.. laravel will handle most of it so you can skip this
- Open the database tab in the top of the right sidebar.
- Click the + icon > Data Source > MySQL
- Create a new source with the following info. Host =
localhost
, Database =SOEN341
,user = root
,password =
(password is blank by default) - You can now use the database viewer inside PHPStorm instead of HeidiSQL.
Just cloned? start here - Ready, Set, Debug! - Compiling front-end - Go back home
Below are some useful coding standards you should abide by.
- Create branches per user story / feature as much as possible.
- Make sure your commit passed CI before making a PR.
- Write descriptive commits that reference issues.
- Specify
fixes | closes #<issue id>
at the end of your commits when appropriate. - HTML & CSS
- Javascript
Below are the minutes from each team meeting.
This is a good place to get help.