restart, reload and disable not working for whitelisted containers.

By default, EasyEngine should configure all new relic plugins upon installation. Following plugins are required per site:

• Nginx(site)
• Nginx(proxy)
• PHP
• MySQL
• Redis

Need to replace the usage of service container names in processes with tags and labels for identification and command execution.

Hence users will be able to know which services can they enable/disable

Currently we have to add newrelic key individually for each site. There should also be a single config key(i.e. newrelic-key) which will add same key in all the sites

Not able to enable services except nginx-proxy on fresh ee install. No message displayed on successful service start.

Currently it's being mount at /opt/easyengine/services/app/db instead it should be mounted at /opt/easyengine/services/db

access and error logs of nginx-proxy point to /dev/stdout and /dev/stderr.

l /opt/easyengine/services/nginx-proxy/logs/
total 8.0K
drwxr-xr-x 2 root root 4.0K Jan  2 03:58 .
drwxr-xr-x 3 root root 4.0K Jan  2 03:58 ..
lrwxrwxrwx 1 root root   11 Nov  7 00:27 access.log -> /dev/stdout
lrwxrwxrwx 1 root root   11 Nov  7 00:27 error.log -> /dev/stderr

We need to mount them correctly.

Service command utility function is trying to do
docker-compose up -d . $container. It should up $service instead.

nginx-proxy reload command is not a simple nginx -t && nginx -s reload. Need to update it to proper reload command.

Every time we create a wp site, just in the beginning we notice these two warnings -

Warning: global-redis: Service already running
Warning: global-db: Service already running

By looking at it, It seems that something is not right. These should not be warnings, but simple info messages or rather we shouldn't even display something as trivial as this, we can simply add it in log file.

Add a service status command that will inform the user of status of the service

The latest develop branch code fails

ee service enable nginx-proxy
PHP Fatal error:  Uncaught Error: Call to undefined function EE\Service\Utils\nginx_proxy_check() in /home/rttest/easyengine/vendor/easyengine/service-command/src/Service_Command.php:55
Stack trace:
#0 [internal function]: Service_Command->enable(Array, Array)
#1 /home/rttest/easyengine/php/EE/Dispatcher/CommandFactory.php(96): call_user_func(Array, Array, Array)
#2 [internal function]: EE\Dispatcher\CommandFactory::EE\Dispatcher\{closure}(Array, Array)
#3 /home/rttest/easyengine/php/EE/Dispatcher/Subcommand.php(425): call_user_func(Object(Closure), Array, Array)
#4 /home/rttest/easyengine/php/EE/Runner.php(276): EE\Dispatcher\Subcommand->invoke(Array, Array, Array)
#5 /home/rttest/easyengine/php/EE/Runner.php(299): EE\Runner->run_command(Array, Array)
#6 /home/rttest/easyengine/php/EE/Runner.php(722): EE\Runner->_run_command_and_exit()
#7 /home/rttest/easyengine/php/EE/Bootstrap/LaunchRunner.php(23): EE\Runner->start()
#8 /home/rttest/easyengine/php/bootstrap.php(75): EE\Bootstrap\LaunchRunner->process(Object(EE\Boots in /home/rttest/easyengine/vendor/easyengine/service-command/src/Service_Command.php on line 55

Steps to reproduce:

1. Create 2 newrelic account.
2. Configure newrelic with first account as shown in https://easyengine.io/handbook/configure-new-relic-in-ee4
3. Wait for newrelic to show data
4. Now change the key to that of 2nd account.
5. Disable and enable site and reload(or stop, kill and start) newrelic daemon container.

Expected output:
The site is registered in 2nd account.

Actual output:
The site is registered in 1st account and does not get re-registered in 2nd account.

I additionally verified it by tailing /var/log/newrelic/newrelic-daemon.log in newrelic daemon while it was starting up in step 5.

Enabling global service fails when /opt/easyengine/services directory has not been created yet. This happens for global services other that nginx-proxy.

So either boot nginx-proxy in this case or add the checks and steps required of proper docker-compose.yml generation for all types of services.

Also, global service ee-global-mariadb needs to be renamed to ee-global-db.

Nginx configuration should be tested using nginx -t before restarting or reloading nginx or nginx-proxy container to avoid restart loop/downtime of the service.

• Global nginx-proxy
• Site's nginx