Which files go up in an Laravel project

Asked

Viewed 727 times

1

Dear, I have an application in Laravel, which I do development on my machine. And I have several clients who use this app, and I have an app for each client. Today I have a server windows server 2012, with all client sites, with database for each client. My question is that I need to know which files I need to upload when doing some correction in the application. I made a . bat that copies the following directories: * app * database * public * Resources * Routes

Today I copy these directories for every application I have. I would like to confirm if these are the folders I should copy or some more?

I wonder if you can help me?

laravel windows

  • Your question seems too vast How To Ask try edit your question

  • 2

    I suggest integrating your server with git, so just do one git commit and then a git push to update only the files that are changed and that you want to be uploaded

2 answers

0

If it is the first deploy you have to upload all the files in the website directory, the folders are:

  • App
  • Bootstrap
  • Config
  • database
  • public
  • Resources
  • Routes
  • Storage
  • tests
  • vendor

if using NPM the folder node_modules will also!

Have some files in the main directory too:

  • .env
  • .htaccess
  • Artisan
  • Composer (2 files)
  • package (2 files)
  • php server.
  • webpack...

If it is not the first deploy you must climb only what has changed!

  • 1

    Climb up node_modules? I think in case it would be better to make one build of the Javascript files and only move them up instead of the directory node_modules integer (which can be significantly weighed depending on the dependencies used).

  • 1

    Interestingly, I figured she was needed even after Build!

  • Lodi, I did this when I went up the first time. It doesn’t make sense to go up the vendor for example, because qdp have to update, I run Composer. I am not working with tests. And the config and Storage folders, are used by the application and also it makes no sense to update... If I’m wrong explain to me....

0

You must climb all but the directory:

  • Vendor
  • Node-modules - using npm
  • .env - because it configures again on the server and well up the . env-example
  • log files

when you are in production only execute the command composer install to move dependencies up in the vendor folder and the npm install the dependencies of the Node-modules folder

  • Iago, I did this when I first went up. I’m not working with tests. E config and specifies folders for each application Already Storage have doubts, but I’ll put in my script.

Browser other questions tagged laravel windows

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