Member Since 5 Years Ago
2,670 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Earned once your experience points ranks in the top 10 of all Laracasts users.
yeah, i understand that. But then i cant really get what the intended deployment path supposed to be like.. whats the point of being able to read the environment variables, unless the code is already in that location.
It not more secure to compile the codes in js , the keys are still public? So, is it best practice to compile after deployment?
i hoped the system would auto generate a "public js" file with the needed environment details and automatic include that script in the html. Maybe i will build it like that someday. But apparently for now, the best and easiest way is to add them to the html and pick it up from there.
but thanks for the response!
Started a new Conversation Laravel Mix Environment Variables - Workflow?
I can't seem to get a clear picture of how this is supposed to work.
i want to compile my JS on 1 machine.. commit it to git and deploy it to an environment. We deploy to test, staging and production via envoyer.
But i want to use the .env to set the environment details for the pusher implementation. i can only get laravel mix to compile the environment variables down at compile time. So they are actually hardcoded in the app.js.
is the idea behind mix to compile at deployment time?
my ideal setup would be to compile it all once and getting the environment variables at runtime.
if there is no way, i will have to expose the data via a variable via html and then pick it up in js. But that seems to me like a nasty workaround.
am i missing something?
ps.. dotenv, tried.. still compiles variables down also testen on clean laravel install.