Integrate Newrelic in Laravel Vapor

David Valbuena — Fri, 07 May 2021 18:10:14 +0000

Using docker-based deployments we can configure newrelic from the same file {env} .dockerfile, here we must install and set the newrelic variables, we must also create an entrypoint.sh file in which we will indicate the image the start of the processes to be carried out:

{env}.dockerfile

FROM laravelphp/vapor:php74

# Download and install newrelic: https://download.newrelic.com/php_agent/release/
RUN \
    curl -L "https://download.newrelic.com/php_agent/release/newrelic-php5-9.16.0.295-linux-musl.tar.gz" | tar -C /tmp -zx && \
    export NR_INSTALL_USE_CP_NOT_LN=1 && \
    export NR_INSTALL_SILENT=1 && \
    /tmp/newrelic-php5-*/newrelic-install install

# add global var to php.ini file
RUN \
    echo $' \n\
    extension = "newrelic.so" \n\
    newrelic.logfile = "/dev/null" \n\
    newrelic.loglevel = "error" \n\
    newrelic.appname = "REPLACE_APP_NAME" \n\ 
    newrelic.license = "REPLACE_NEWRELIC_LICENCE"' >> /usr/local/etc/php/php.ini

# Remove newrelic.ini file
RUN rm /usr/local/etc/php/conf.d/newrelic.ini

RUN mkdir -p /usr/local/etc/newrelic && \
  echo "loglevel=error" > /usr/local/etc/newrelic/newrelic.cfg && \
  echo "logfile=/dev/null" >> /usr/local/etc/newrelic/newrelic.cfg

COPY . /var/task

USER root
RUN chmod +x /var/task/entrypoint.sh
ENTRYPOINT ["/var/task/entrypoint.sh"]

The entrypoint.sh file is necessary to start the execution of PHP and indicate the type of process that will be carried out with newrelic

#! /bin/sh

#start Newrelic daemon
newrelic-daemon -c /usr/local/etc/newrelic/newrelic.cfg

#start PHP
/opt/bootstrap

newrelic_background_job(false);

The newrelic.ini file was removed because it generates the following run-time error:

Therefore, the setting of the variables to the php.ini file is carried out, which loads the default options of newrelic.

Laravel 7: Cache route error

David Valbuena — Wed, 21 Oct 2020 21:29:32 +0000

It is common to create laravel projects in subfolders, and perform an access configuration by subdomains, something similar to: https://mydomain.com/aliasdomain , generally, this has been supported and at the time of caching the routes hasn't been generated a type of conflict, however, in laravel 7 this has generated a mistake in the routes that are specified as:

Route::get('/', '.....')

A solution implemented in a project to solve this problem with the route cache was:

Create a middleware with the following validation:

class RouteCache 
{
    public function handle(Request $request, Closure $next)
    {
        if ($request->path() === '/') {
            $newURI = $request->server->get('REQUEST_URI') . 'index.php';
            $request->server->set('REQUEST_URI', $newURI);
        }

        return $next($request);
    }
}

Add the middleware to the Kernel file in the middleware array:

protected $middleware = [
    ....,
    \App\Http\Middleware\RouteCache::class,
];

With this, what is achieved is that if a route / is declared within the project, the middleware validates when trying to access it and overwrites the REQUEST_URI value that the request carries by adding index.php (this will continue being transparent to the end user)

DEV Community: David Valbuena

Integrate Newrelic in Laravel Vapor

Laravel 7: Cache route error