Setting up Kubernet and Laravel or Laravel on Docker can be tedious. Hell, setting up Laravel on multiple servers can be a real pain. Been doing research on setting up
Laravel
Articles categorized in: Laravel
To have ESLint play nice with Laravel a few things have to be taken care of. Packages have to be installed, configuration has to be done, Webpack Mix adjusted, .eslintignore
We have been working on a Laravel setup where we bill customers using pay.nl using their API and E-boekhouden.nl for the bookkeeping. The reason being that they both offer APIs
Sometimes you want to remove a directory but keep it locally on your box. So you want to exclude it from the repository, but keep it locally. Need We wanted
To increate PHP memory usage edit the following file: nano /usr/local/etc/php/7.4/conf.d/php-memory-limits.ini You can get the details on your PHP ini using php –ini and then do a valet restart to
On upgrading to Laravel 6 we ran into issues locally running predis. This as no client was set in .env and now config was going for native PHP Redis or
If you want to upgrade Laravel to the latest you can use Laravelshift which is really cool. But you can do this manually with git as well. In this example
If you want to send Laravel form data using Sendgrid use this for .env (using your own details of course): MAIL_DRIVER=smtp MAIL_HOST=smtp.sendgrid.net MAIL_PORT=587 MAIL_USERNAME=apikey MAIL_PASSWORD=very_long_key MAIL_ENCRYPTION=tls MAIL_FROM_NAME=”Company Name” MAIL_FROM_ADDRESS=info@domain.com The
Normally Laravel has authentication including email verification built in. Since Laravel 5.7 I believe. But sometimes you need it added as you have a Laravel application that predates all this.
Local testing of Pay.NL can be a challenge. Error messages given out are often vague to say the least and documentation is not always great either. We just updated our
We are considering moving from Forge to Vapor or from VMs to Serverless for a client. We are however not convinced that the startup in question will benefit from it.
Just spent several hours yesterday understanding why we hit a CORS No “Access Control Allow Origin” header present issue again. Read loads about common Cross Origin Resource Sharing (CORS) again.