This items are based on feedback that I had on the first time I touched on Laravel stuff.
[Mário's tutorial] (https://www.youtube.com/watch?v=D1D2g7yEgCM&feature=youtu.be).
- At the root of your project, run
vi .homestead/Homestead.yaml
- Add all jobs in sites section
- Add also the website on your hosts file -
sudo vi /etc/hosts
- Save and exit
- Run
cd Homestead > vagrant provision
- to new jobs added - Run
cd Homestead > vagrant up
- to jobs that already live there
On the directory that we want to create the job path - Documents/jobs/dev, p. ex....
composer create-project laravel/laravel project-name
To generate key, run php artisan key:generate
or go to [Laravel Recipes] (http://laravel-recipes.com/recipes/283/generating-a-new-application-key) and copy
and paste
it.
- Run
composer install
- Run
npm install
- Run
bower install
- Run
gulp
- If you clone a project and gives error on the main screen, thats you need to run
sudo composer install
- And then go to [Laravel Recipes] (http://laravel-recipes.com/recipes/283/generating-a-new-application-key) to generate a new key, duplicate the
.env.example
file, rename to just.env
and paste the key inAPP_KEY
Error: Cannot find module 'laravel-elixir'
. To resolve this, do this, you need to runnpm install
npm ERR! EEXIST, open
[...]bdfc06e-pm-source-map-0-1-43-package-tgz.lock Move it away, and try again.
That's because your node version is getting errors, as you can see here. The solution that I had was reinstall the node. What I've done:
- Run
brew uninstall node
brew install node
sudo brew postinstall node #
brew error message provided this recommendation; only worked with sudo- Then
npm install
again.
Or even try:
- Run
npm -g install npm@next
ornpm -g install npm@2.1.1
.
Yeah, at Din we work with two areas: the panel and the website.
First of all, let's talk about admin area. Follow these steps:
- Clone the repo
- Create the schema on MYSQL Workbench
- Sync the database
- Import the stuff on
vagrant ssh
- Run
composer update
- Create and edit your
config.local.php
file
The end, by now.
So, follow these steps now:
- Update your repo going to
dev
branch, or whatever is the development branch - Delete
rm -rf
thevendor
directory - DO NOTDelete
rm -rf
thecomposer.lock
file. Credits to Levi - Run
composer install
Probably this area is working now.