Member Since 1 Year Ago
4,450 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.
I'm running into this as well (laravel 6, here). Had to disable emailoutput :(
I followed several tutorials and did all the important steps:
changed the user model to include that new field the in fillables:
protected $fillable = ['name', 'email', 'password','timezone' ];
and changed the create method of the RegisterController to:
return User::create([ 'name' => $data['name'], 'email' => $data['email'], 'password' => Hash::make($data['password']), 'timezone' => $data['timezone'], ]);
Like I said, everything is saved in the database, and if the user logs out and in again it works fine, but immediately after registration the new field seems to be not loaded.
Started a new Conversation Can't Properly Add A New Field To Registration Flow
So I edited the registration view and controller (provided by Auth), to include a timezone field.
Everything works and the field is saved in the database.
The problem is that its not available when I do auth()->user()->timezone, unless I log out and log in again. Am I missing some step so that that value is loaded to the user model after registration?
I dont use supervisor, since the workers are running continuously. I understood that was the main point of supervisor so it didn't make sense to me
Hi @drewdan and thanks!
Unfortunately I need to connect to an O365 server for the mail sending part, no luck there.
The workers quit after processing the queue (not running continuously) and I'm starting them via cron jobs (using the laravel scheduler). So maybe I could have a small script that fires N workers at the same time? What's a reasonable N? :)
Started a new Conversation Sending Batches Of Mails Is Extremely Slow. Can We Parallelize It?
I need to send notification emails at a specific time every day, for hundreds of users.
I created a Mailable class that implements ShouldQueue, and then I run my queues manually every once in a while.
The problem is that every user gets its own customized email, so I get hundreds of individual emails to be processed. Perhaps is due to the connection to the SMTP server, but my queue seems to take 1-2seconds per email, which means is extremely slow to get it all done!
I'm probably missing something here... can I parallelize it in some way? Or a better way to send it as a batch?
thanks in advance
Started a new Conversation Should I Docker-ize For Production?
I'm finishing off a product for a client and the production server the client is running is quite outdated (ubuntu 16.04). I'm using MySQL 8 which is not even available in the package repositories. At the same time, I'm not confident to be upgrading their server and possibly messing up something they have there running ok for the past years.
So I was considering just having containers for nginx(+php), mysql and then pull the laravel app inside. Is it better to have a container for each (nginx, mysql), or one that includes everything?
Any advice on this from people who have been through similar situations?