Envoyer and Elixir

You should run elixir on your development environment and then push the compiled assets to your online service ;) This way you don't have to worry about any compiling on the server

Hi @bobbybouwmann . But the build folder will keep changing. is that a best practice to keep adding the build folder?

For now it is, since there is not really anything that can make this process easier. Unless you want to compile everything on your production server as well on every deployment.

Here is another thread on the same subject: https://laracasts.com/discuss/channels/elixir/elixir-best-practices-run-on-every-deploy

@bobbybouwmann One more question. I've tried search at Google but no luck. Is there any way to make .gitignore for specific branch?

I want to apply like you said. Deploy the compiled version to the production branch. But at development I want to ignore it.

THanks.

With Laravel and Elixir you only need to have the public directory in version control. So every time you compile something the public directory is updated with the new styles and javascript. You can then simply push that to the server. Even with elixir versioning enables, since the build directory will be pushed then.

This means that you don't have to push your assets to your repo or production server, since it's all compiled in your build directory ;)