Design versioning Standard 5.1

Asked

Viewed 341 times

3

I do a project in Laravel 5.1 and use the XAMPP and all settings as database this site,(home computer) etc. Only I went up (push) for Github this project only when I go on the work PC I clone the project and it doesn’t work logical.

Why not have the database in this case I have to configure the file .env? And recreate the database? And have some other file I have to configure?

php laravel-5 versioning

  • Bro, if you’re actually pulling the configs from . env is just that, change it as needed, create the bd and run the migrate.

  • php Artisan make:migrate type so?

  • 2

    php Artisan migrate

  • I noticed that the file . env when I gave a push did not come, I had to recreate

  • 1

    usually it doesn’t even go git in push, ai you use .env.example to create your . env in the place that will work

  • That’s why people have to start using migrate, rather than simply making a "dumpling" from Phpmyadmin

  • @Raylan Soares thank you in this case when doing the configuration of the bank instead of using the . env, I use .env.example, and what about the app_key? file I paste the file . env?

  • no, you will copy ".env.example" and rename the copy to ". env" and fill in the data

  • 1

    how much key I think q just give a "php Artisan key:generate"

  • thanks for the help

Show 5 more comments

1 answer

3


The archive .env is only on the machine we are working on, when we send the project to git that file is usually not sent.

To configure your application in another workplace do the following:

  1. Clone your git project.
  2. Create a copy of .env.example, rename to .env and fill in with the local data.
  3. Create your database.
  4. run a migrate: php artisan migrate.

Obs: To generate a new key just run the command php artisan key:generate.

Browser other questions tagged php laravel-5 versioning

You are not signed in. Login or sign up in order to post.