Command-line control panel for Nginx Server to manage WordPress sites running on Nginx, PHP, MySQL, and Let's Encrypt

Last update: May 22, 2022

EasyEngine Logo

EasyEngine v4 Build 🔨 + Test 👨‍🔧 Join EasyEngine Slack Channel Latest Stable Version License

EasyEngine makes it greatly easy to manage nginx, a fast web-server software that consumes little memory when handling increasing volumes of concurrent users.

Handcrafted Enterprise WordPress Solutions by rtCamp

Requirements

  • Docker
  • Docker-Compose
  • PHP CLI (>=7.1)
  • PHP Modules - curl, sqlite3, pcntl

Installing

Linux

For Linux, we have created an installer script which will install all the dependencies for you. We have tested this on Ubuntu 14.04, 16.04, 18.04 and Debian 8, Debian 10.

wget -qO ee https://rt.cx/ee4 && sudo bash ee

Even if the script doesn't work for your distribution, you can manually install the dependencies and then run the following commands to install EasyEngine

wget -O /usr/local/bin/ee https://raw.githubusercontent.com/EasyEngine/easyengine-builds/master/phar/easyengine.phar
chmod +x /usr/local/bin/ee

Tab completions

EasyEngine also comes with a tab completion script for Bash and ZSH. Just download ee-completion.bash and source it from ~/.bash_profile:

source /FULL/PATH/TO/ee-completion.bash

Don't forget to run source ~/.bash_profile afterwards.

If using zsh for your shell, you may need to load and start bashcompinit before sourcing. Put the following in your .zshrc:

autoload bashcompinit
bashcompinit
source /FULL/PATH/TO/ee-completion.bash

Usage

To get started with EasyEngine and create a wordpress site, run

ee site create example.com --type=wp

Need a wordpress site with caching? Try

ee site create example.com --type=wp --cache

Need a wordpress multi-site with page cache?

ee site create example.com --type=wp --mu=wpsubdir --cache

Need a plain and simple html site?

ee site create example.com

Want to play around with your new site?

ee shell example.com

Want to know more? Checkout readme of these commands -

Note: ⚠️ EasyEngine will currently only run with root privileges. You can run ee help, ee help site and ee help site create to get all the details about the various commands and subcommands that you can run.

Development

Development of easyengine is done entirely on GitHub.

We've used wp-cli framework as a base and built EasyEngine on top of it.

This repo contains main core of easyengine (the framework). All top level commands(except ee cli) i.e. ee site, ee shell have their own repos.

Currently we have following commands which are bundled by default in EasyEngine:

In future, community will be able to make their own packages and commands!

Contributing

We warmheartedly welcome all contributions however and in whatever capacity you can either through Pull Requests or by reporting Issues. You can contribute here or in any of the above mentioned commands repo.

Donations

PayPal-Donate

GitHub

https://github.com/EasyEngine/easyengine
Comments
  • 1. php5-fpm pools (shared-hosting model)

    Is it possible to determine/create php pools for each site? I would like to run every site with custom users and groups and not all with www-data

    like: ee site create mysite.com --wp --umyuserr:gmygroup

    Then ee create the php-fpm .conf file and the user:group.

    I'm doing this manually every time.

    Reviewed by andremacola at 2014-03-06 23:29
  • 2. Unable to run apt-get install - When trying to create new site.

    Hi,

    I just setup EE on a fresh DigitalOcean Droplet and whenever i try to create a new site using ee site create domain.com --php it ends up throwing Unable to run apt-get install.

    What's wrong?

    Reviewed by irazasyed at 2015-03-20 11:32
  • 3. HipHop Support

    Hi,

    It seems HipHop support is nice, they have prebuilt packages, and perform quite better than php5-fpm. Not much changing codes I guess.

    Here, take a look at this: https://github.com/facebook/hhvm/wiki#installing-pre-built-packages-for-hhvm

    Reviewed by duajanuari at 2014-04-12 05:36
  • 4. Http/2 Support ?

    Nginx 1.9.5 is supporting http/2 protocol. But EasyEngine's nginx version is 1.8. Chrome will remove SPDY support in early 2016. Is there any plan about HTTP/2 support?

    Reviewed by vefaliahmet at 2015-10-26 12:39
  • 5. Future of W3 Total Cache and WP Super Cache in EE [feedback-request]

    We use only nginx fastcgi_cache for full page caching i.e. wpfc option in ee site create command.

    WP Super Cache is only used for full page caching so we never used it.

    W3 Total Cache is generally used for many things, but have replacement already for few features and planned replacement for few other features.

    1. Full page cache (Nginx fastcgi_cache is replacement)
    2. Object Cache - redis and memcache - both have object-cache.php (testing is underway)
    3. Database Cache - not required. I feel this is "over"caching. MySQL query cache and Object Cache together does decent job.
    4. CDN - Origin/Pull CDN can be done using nginx. For S3-style CDN, many plugins exist.
    5. Minify/Combine - Can be done in pagespeed but pagespeed has open issue. But there are wordpress plugins for this and one of them wp-minify - https://wordpress.org/plugins/wp-minify/ worked nice for me in past.

    So we want to know, if we drop support for above 2 plugins in near feature, will it affect you? If yes, how?

    One way is to move these options to ee plugins and let those who need them, manage it.

    Please provide your feedback. Having less options will help us focus on improvements.

    Reviewed by rahul286 at 2015-04-24 10:34
  • 6. ee uninstall option

    There should be an option if someone wants to completly remove ee from the system.

    You might want to warn them but let the user have an option to remove ee completely.

    Reviewed by anantshri at 2015-04-11 13:38
  • 7. Single WordPress With SubDirectory

    set $dir "";
    if ($request_uri ~ ^/([^/]*)/.*$ ) {
          set $dir1 /$1;
    }
    location / {
          try_files $uri $uri/  $dir1/index.php?$args;
     }
    
    
    Reviewed by MiteshShah at 2013-07-24 15:26
  • 8. Blitz timeouts with EasyEngine [pagespeed issue]

    Did a quick comparison of the same site on two instances:

    1. with W3TC Page (memcached), Object Cache (memcached), and W3TC Browser cache enabled. - My current setup

    2. with EasyEngine Nginx fastcgi cache, Nginx Browser cache, and w3tc object cache (memcached).

    Test site was a copy of real full wordpress site with more than 500 posts.

    Attached are the Blitz results. EE Nginx settings are default. I am not sure if EE Nginx settings should be optimized but I am surprised to see the big difference. @rahul286 any thoughts would be much appreciated.

    new-1

    Reviewed by htpcBeginner at 2015-04-16 19:28
  • 9. PHP5-FPM consuming all CPU, 504 Gateway Time Out

    OS: Ubuntu 12.04 i386; 3.8.0-29-generic (current updates as of now) EasyEngine: 1.3.0

    This system has 512 MB of RAM, so it is a bit small. I create a site with --wpfc and it works fine ("shell" WP site) Then I install 15 plugins I had installed on my backed up WP site (which was hosted elsewhere also with 512MB RAM but on Apache) and it's still working fine. Then I restore the main DB and PHP5-FPM goes wild:

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4539 www-data 20 0 100m 14m 9760 R 15.3 2.9 0:45.78 php5-fpm 4533 www-data 20 0 102m 27m 21m R 14.9 5.6 1:05.74 php5-fpm 4535 www-data 20 0 100m 24m 19m R 14.9 5.0 1:06.02 php5-fpm 4544 www-data 20 0 100m 14m 9788 R 14.9 2.9 0:07.60 php5-fpm 4545 www-data 20 0 100m 14m 9776 R 14.9 2.9 0:07.54 php5-fpm 4538 www-data 20 0 100m 19m 14m R 14.6 3.9 0:24.43 php5-fpm ... I used default EE settings for everything. I tried adjusting some PHP5-FPM parameters and I recreated the entire site but I can't get around it.

    I set "pm = ondemand" in www.conf and that seems to have helped a bit, but only initially and now I'm back to the same situation (the max. number of servers is now set to 4, so php5-fpm processes are consuming close to 100% of CPU). It seems that default values set in EE are quite high...

    Any idea what could be wrong here? This WP site is basically idle and there are no other services except what's started by EE so it should be able to show pages.

    Update 1: I tried various things, like "--wp" (same issue), "--w3tc" (same) and with 1GB RAM (same).

    I get this error in Nginx: 2014/04/13 17:33:01 [error] 16221#0: *3 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 1.2.3.4, server: domain.com, request: "GET /wp-login.php?redirect_to=http%3A%2F%%2Fdomain.com%2Fwp-admin%2F&reauth=1 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "domain.com"

    Reviewed by ghost at 2014-04-13 10:46
  • 10. Only homepage caches, and Let's Encrypt certification conflict with EE 4 RC1

    If you feel the issue is an EasyEngine core specific issue, please attach the output of the following commands.

    System Information

    • No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic
    • EE 4.0.0-rc.1
    • +-------------------+----------------------------------------------------------+ | OS | Linux 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02: | | | 16 UTC 2018 x86_64 | | Shell | /bin/bash | | PHP binary | /usr/bin/php7.2 | | PHP version | 7.2.11-3+ubuntu18.04.1+deb.sury.org+1 | | php.ini used | /etc/php/7.2/cli/php.ini | | EE root dir | phar://ee.phar | | EE vendor dir | phar://ee.phar/vendor | | EE phar path | /root | | EE packages dir | | | EE global config | /opt/easyengine/config/config.yml | | EE project config | | | EE version | 4.0.0-rc.1 | +-------------------+----------------------------------------------------------+
    • wp: command not found

    So I wanted to test out RC1 last night and did so on a fresh install of Wordpress.

    I used the command. . .

    • ee site create shaylahleigh.com --type=wp --cache --admin-user=user--admin-pass=pass --ssl=le

    to create the site and then just published some test posts. The NGINX Helper plugin was installed and activated, and the WP Redis plugin was installed and activated (which they should be, I presume).

    However, only my homepage was being cached.

    Opening up a Chrome incognito tab and going to the website ShaylahLeigh.com (was the URL I tested this install on), and then opened up the Chrome console before switching to the network tab.

    I saw HIT/BYPASSon the home page (which indicates a cached page), but any other post that I went to (even when switching back and forth between the homepage and any of the four posts) showed BYPASS/BYPASS to indicate that the page wasn't being cached for some reason.


    The second issue brought up in the title has to do with the Let's Encrypt certification. With EasyEngine 3, I could create my website using its compatible command listed above, and then go into Settings -> General and change the website URL from just blah.com to www.blah.com.

    I have 7 or so websites up on EasyEngine 3 using this method and the Let's Encrypt certification works on the www. version just like it works on the non-www. version (Even though WordPress does a redirect to the www. version.

    However, as you can see from going to ShaylayLeigh.com I am getting told the following error. . .

    "This server could not prove that it is www.shaylahleigh.com; its security certificate is from shaylahleigh.com. This may be caused by a misconfiguration or an attacker intercepting your connection."

    Reviewed by Endda at 2018-11-03 15:31
  • 11. Broken after upgrade

    Today I did a ee update becuase it's been a while. Now ee is broke for me.

    • ee site create demo.redux.io --wpfc
      • Downloading WP-CLI [Errno 2] No such file or directory: '/usr/bin/wp'
    • [email protected]:/usr/bin# ee --version
      • EasyEngine v3.0.5
      • Copyright (c) 2015 rtCamp Solutions Pvt. Ltd.

    Any ideas?

    Reviewed by dovy at 2015-03-18 20:03
  • 12. [release] easyengine.phar is not uploaded for the 4.5.5 release

    This issue tracker is only for issues related to EasyEngine. Please use https://github.com/EasyEngine/easyengine/discussions for support questions.

    If you feel the issue is a EasyEngine specific issue, please attach the output of the following commands.

    System Information

    • [ ] ee cli info
    • [ ] lsb_release -a
    • [ ] docker version
    • [ ] docker-compose version

    not quite sure if this should go to discussion or not. Thanks!

    Reviewed by chenrui333 at 2022-05-01 21:52
  • 13. Failed to create 'themes' or 'plugins' directories if the `--skip-content` flag is used.

    The following command is used to create a new site.

    ee site create example.com --type=wp --title=XX --admin-user=xxx --skip-content --ssl=le
    

    Attention to --skip-content flag.

    After the installation is done, WP works great.

    But if I try to install a theme or a plugin, it will fail, because can't create the respective directories.

    Installation failed: Could not create directory.
    

    This issue has been there for years, and I always created these dirs manually and set the needed permissions. But would be great the have them created automatically.

    The uploads folder does not have this problem. It's created automatically on the first file upload.

    System Information

    • On any EE v4. This issue has been there in all Ubuntu dist that I've used: 16.04 --- 20.04
    Reviewed by awps at 2022-03-30 06:37
  • 14. Why latest distros not supported?

    Latest today version is project dead? https://easyengine.io/faq/ Q 9. Which operating systems are supported by EasyEngine? v3 and v4 support Ubuntu version 12.04 , 14.04, 16.04, 18.04 and Debian 7 & 8.

    CentOS or any other Linux Distro is not currently supported. They are also not on the product roadmap in the near future.

    Reviewed by kangarooo at 2022-03-07 20:07
  • 15. Codes dont work

    Latest version today

    [email protected]:~# ee site create myxxdoman.com --wpsubdomain --wpredis Error: Parameter errors: unknown --wpsubdomain parameter

    Instructions from https://easyengine.io/wordpress-nginx/tutorials/multisite/subdomains/redis_cache-conditional-purging-optional-domain-mapping/

    Reviewed by kangarooo at 2022-03-07 20:04
  • 16. A typographical error - insteed of _ in creating global db service when doing "ee service enable db" on homebrew easyengine

    Hello and thank you all who are working on Easyengine Im really grateful for your work you put in to it. This is my first Issue-report so bear with me. I think the issue is related to a discussion in https://github.com/EasyEngine/easyengine/discussions/1659 Originally posted by venkateshwarans January 22, 2022.

    The problem occurs with fresh installation on mac with homebrew installations of easyengine. After a unproblematic installation I run the command "ee service enable db" and it creates the "services-global-db-1" docker container. Log shows: [27-02-2022 23:37:36] ee.DEBUG: argv: /opt/homebrew/bin/ee service enable db
    [27-02-2022 23:37:36] ee.DEBUG: Running command: service enable
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: COMMAND: ip route show | cut -d ' ' -f1 | grep ^10
    [27-02-2022 23:37:36] ee.DEBUG: STDERR: sh: ip: command not found
    [27-02-2022 23:37:36] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: COMMAND: ip route show | cut -d ' ' -f1 | grep ^10
    [27-02-2022 23:37:36] ee.DEBUG: STDERR: sh: ip: command not found
    [27-02-2022 23:37:36] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: COMMAND: which docker
    [27-02-2022 23:37:36] ee.DEBUG: RETURN CODE: 0
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: COMMAND: docker inspect -f '{{.State.Running}}' services_global-db_1
    [27-02-2022 23:37:36] ee.DEBUG: STDOUT:
    [27-02-2022 23:37:36] ee.DEBUG: STDERR: Error: No such object: services_global-db_1
    [27-02-2022 23:37:36] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: COMMAND: which docker
    [27-02-2022 23:37:36] ee.DEBUG: RETURN CODE: 0
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: COMMAND: docker inspect -f '{{.State.Running}}' services_global-db_1
    [27-02-2022 23:37:36] ee.DEBUG: STDOUT:
    [27-02-2022 23:37:36] ee.DEBUG: STDERR: Error: No such object: services_global-db_1
    [27-02-2022 23:37:36] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: -----------------------
    [27-02-2022 23:37:36] ee.DEBUG: COMMAND: docker-compose -f docker-compose.yml up -d global-db
    [27-02-2022 23:37:36] ee.DEBUG: STDERR: Network ee-global-frontend-network Creating Network ee-global-frontend-network Created Network ee-global-backend-network Creating Network ee-global-backend-network Created Container services-global-db-1 Creating Container services-global-db-1 Created Container services-global-db-1 Starting Container services-global-db-1 Started
    [27-02-2022 23:37:36] ee.DEBUG: RETURN CODE: 0

    Running the command "ee service enable nginx-proxy creates the services_nginx-proxy_1 container all fine.

    Running the command "ee site create testsite.test --type=wp" results in a error with no site created.

    When I change the name (with docker rename function) of my container from "service-global-db-1" to "services_global-db_1" the command "ee site create testsite.test --type=wp" works fine without any problem 👍.

    I think there is a typo somewhere in the EE code but I don't have the skills to find it (although I did try). That typo lead to a more cryptic uncaught error message in the terminal verbose about a fatal error involving symfony trying to rename a file that probably don't exist. That terminal information lead me on a wild google ghost hunt involving MacOS, writepermisson, chmod, docker, ee, /etc/hosts and a lot of trying and failing with a factoryreset of my mac as a result. Let me tell you it didn't end well 😳😂👍.

    Anyway. I have been able to reproduce the error and fixing it the same way every time (renaming the container to "services_global-db_1". Im pretty sure its a typo somewhere in the EE code and if it isn't then Im really sorry. I did notice that the docker-compose.yml doesn't contain a name for the global db but for the nginx-proxy. Maybe that has something to do with it?

    This is the log for command "ee site create testsite.test --type=wp.

    Log show all good for the first part with nginx-proxy the rest is a bit of a problem. [27-02-2022 23:42:43] ee.DEBUG: COMMAND: docker inspect -f '{{.State.Running}}' services_global-db_1
    [27-02-2022 23:42:43] ee.DEBUG: STDOUT:
    [27-02-2022 23:42:43] ee.DEBUG: STDERR: Error: No such object: services_global-db_1
    [27-02-2022 23:42:43] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:42:43] ee.DEBUG: -----------------------
    [27-02-2022 23:42:43] ee.DEBUG: COMMAND: which docker
    [27-02-2022 23:42:43] ee.DEBUG: RETURN CODE: 0
    [27-02-2022 23:42:43] ee.DEBUG: -----------------------
    [27-02-2022 23:42:43] ee.DEBUG: COMMAND: docker inspect -f '{{.State.Running}}' services_global-db_1
    [27-02-2022 23:42:44] ee.DEBUG: STDOUT:
    [27-02-2022 23:42:44] ee.DEBUG: STDERR: Error: No such object: services_global-db_1
    [27-02-2022 23:42:44] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:42:44] ee.DEBUG: -----------------------
    [27-02-2022 23:42:44] ee.DEBUG: -----------------------
    [27-02-2022 23:42:44] ee.DEBUG: COMMAND: docker-compose -f docker-compose.yml up -d global-db
    [27-02-2022 23:42:44] ee.DEBUG: STDERR: Container services-global-db-1 Running
    [27-02-2022 23:42:44] ee.DEBUG: RETURN CODE: 0
    [27-02-2022 23:42:44] ee.DEBUG: -----------------------
    [27-02-2022 23:42:44] ee.DEBUG: -----------------------
    [27-02-2022 23:42:44] ee.DEBUG: COMMAND: docker cp /var/folders/n_/4xgkzj2s6zsby7ws4ss85qh00000gn/T/db_exec services_global-db_1:/db_exec
    [27-02-2022 23:42:44] ee.DEBUG: STDERR: Error: No such container:path: services_global-db_1:/
    [27-02-2022 23:42:44] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:42:44] ee.DEBUG: -----------------------
    [27-02-2022 23:42:44] ee.DEBUG: -----------------------
    [27-02-2022 23:42:44] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec
    [27-02-2022 23:42:44] ee.DEBUG: STDERR: Error: No such container: services_global-db_1
    [27-02-2022 23:42:44] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:42:44] ee.DEBUG: -----------------------

    _This repeats for a about 11 seconds and about 400 rows 😊 and then continues with: _

    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: COMMAND: docker cp /var/folders/n_/4xgkzj2s6zsby7ws4ss85qh00000gn/T/db_exec services_global-db_1:/db_exec
    [27-02-2022 23:43:55] ee.DEBUG: STDERR: Error: No such container:path: services_global-db_1:/
    [27-02-2022 23:43:55] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec
    [27-02-2022 23:43:55] ee.DEBUG: STDERR: Error: No such container: services_global-db_1
    [27-02-2022 23:43:55] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.INFO: ======================== site cleanup start ========================
    [27-02-2022 23:43:55] ee.WARNING: Could not create user testsite.test-2JsxTn. Please check logs.
    [27-02-2022 23:43:55] ee.WARNING: Initiating clean-up.
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: COMMAND: docker volume ls --filter="label=org.label-schema.vendor=EasyEngine" --filter="label=io.easyengine.site=testsite.test" -q
    [27-02-2022 23:43:55] ee.DEBUG: RETURN CODE: 0
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: COMMAND: docker cp /var/folders/n_/4xgkzj2s6zsby7ws4ss85qh00000gn/T/db_exec services_global-db_1:/db_exec
    [27-02-2022 23:43:55] ee.DEBUG: STDERR: Error: No such container:path: services_global-db_1:/
    [27-02-2022 23:43:55] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec
    [27-02-2022 23:43:55] ee.DEBUG: STDERR: Error: No such container: services_global-db_1
    [27-02-2022 23:43:55] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: -----------------------
    [27-02-2022 23:43:55] ee.DEBUG: COMMAND: docker cp /var/folders/n_/4xgkzj2s6zsby7ws4ss85qh00000gn/T/db_exec services_global-db_1:/db_exec
    [27-02-2022 23:43:56] ee.DEBUG: STDERR: Error: No such container:path: services_global-db_1:/
    [27-02-2022 23:43:56] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:43:56] ee.DEBUG: -----------------------
    [27-02-2022 23:43:56] ee.DEBUG: -----------------------
    [27-02-2022 23:43:56] ee.DEBUG: COMMAND: docker exec services_global-db_1 sh db_exec
    [27-02-2022 23:43:56] ee.DEBUG: STDERR: Error: No such container: services_global-db_1
    [27-02-2022 23:43:56] ee.DEBUG: RETURN CODE: 1
    [27-02-2022 23:43:56] ee.DEBUG: -----------------------
    [27-02-2022 23:43:56] ee.WARNING: An Error occurred. Initiating clean-up.
    [27-02-2022 23:43:56] site-command.ERROR: Type: 1
    [27-02-2022 23:43:56] site-command.ERROR: Message: Uncaught Symfony\Component\Filesystem\Exception\IOException: Cannot rename "/private/var/folders/n_/4xgkzj2s6zsby7ws4ss85qh00000gn/T/hosts0Hj1iv" to "/etc/hosts". in phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/symfony/filesystem/Filesystem.php:290 Stack trace: #0 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/symfony/filesystem/Filesystem.php(692): Symfony\Component\Filesystem\Filesystem->rename('/private/var/fo...', '/etc/hosts', true) 1 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/easyengine/site-command/src/helper/site-utils.php(759): Symfony\Component\Filesystem\Filesystem->dumpFile('/etc/hosts', '##\n# Host Datab...') 2 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/easyengine/site-command/src/helper/class-ee-site.php(274): EE\Site\Utils\remove_etc_hosts_entry('testsite.test') 3 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/easyengine/site-type-wp/src/WordPress.php(1606): EE\Site\Type\EE_Site_Command->delete_site(0, 'testsite.test', '/Users/releez/e...', Array) 4 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/easyengine/site-type-wp/src/WordPress.php(408): EE\Site\Type\WordPress->catch_clean(Object(Exception)) 5 [internal function]: EE\Site\Type\WordPress->create(Array, Array) 6 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Dispatcher/CommandFactory.php(96): call_user_func(Array, Array, Array) 7 [internal function]: EE\Dispatcher\CommandFactory::EE\Dispatcher{closure}(Array, Array) 8 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Dispatcher/Subcommand.php(272): call_user_func(Object(Closure), Array, Array) 9 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Runner.php(334): EE\Dispatcher\Subcommand->invoke(Array, Array, Array) 10 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/class-ee.php(1184): EE\Runner->run_command(Array, Array) 11 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/easyengine/site-command/src/Site_Command.php(154): EE::run_command(Array, Array) 12 [internal function]: Site_Command->__invoke(Array, Array) 13 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Dispatcher/CommandFactory.php(96): call_user_func(Array, Array, Array) 14 [internal function]: EE\Dispatcher\CommandFactory::EE\Dispatcher{closure}(Array, Array) 15 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Dispatcher/Subcommand.php(272): call_user_func(Object(Closure), Array, Array) 16 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Runner.php(334): EE\Dispatcher\Subcommand->invoke(Array, Array, Array) 17 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Runner.php(357): EE\Runner->run_command(Array, Array) 18 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Runner.php(783): EE\Runner->_run_command_and_exit() 19 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/EE/Bootstrap/LaunchRunner.php(23): EE\Runner->start() 20 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/bootstrap.php(74): EE\Bootstrap\LaunchRunner->process(Object(EE\Bootstrap\BootstrapState)) 21 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/init-ee.php(27): EE\bootstrap() 22 phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/php/boot-phar.php(8): include('phar:///opt/hom...') 23 /opt/homebrew/Cellar/easyengine/4.5.3/bin/ee(5): include('phar:///opt/hom...') 24 {main} thrown
    [27-02-2022 23:43:56] site-command.ERROR: File: phar:///opt/homebrew/Cellar/easyengine/4.5.3/bin/ee/vendor/symfony/filesystem/Filesystem.php
    [27-02-2022 23:43:56] site-command.ERROR: Line: 290
    [27-02-2022 23:43:56] ee.WARNING: Exiting gracefully after rolling back. This may take some time.

    System Information

    • ee cli info

    OS | Darwin 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T8101 arm64 Shell | /bin/zsh
    PHP binary | /opt/homebrew/Cellar/php/8.1.3/bin/php
    PHP version | 8.1.3
    php.ini used | /opt/homebrew/etc/php/8.1/php.ini
    EE root dir | phar://ee.phar
    EE vendor dir | phar://ee.phar/vendor
    EE phar path | /Users/myuser
    EE packages dir |
    EE global config | /Users/releez/easyengine/config/config.yml
    EE project config |
    EE version | 4.5.3

    • sw_vers; ProductName: macOS ProductVersion: 12.2.1 BuildVersion: 21D62

    • docker version: Client: Cloud integration: v1.0.22 Version: 20.10.12 API version: 1.41 Go version: go1.16.12 Git commit: e91ed57 Built: Mon Dec 13 11:46:56 2021 OS/Arch: darwin/arm64 Context: default Experimental: true Server: Docker Desktop 4.5.0 (74594) Engine: Version: 20.10.12 API version: 1.41 (minimum version 1.12) Go version: go1.16.12 Git commit: 459d0df Built: Mon Dec 13 11:43:07 2021 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.4.12 GitCommit: 7b11cfaabd73bb80907dd23182b9347b4245eb5d runc: Version: 1.0.2 GitCommit: v1.0.2-0-g52b36a2 docker-init: Version: 0.19.0 GitCommit: de40ad0

    • Docker Compose version 2.2.3

    Reviewed by Plendix at 2022-02-28 01:23
  • 17. Getting error when creating WP (warning could not create user

    This issue tracker is only for issues related to EasyEngine. Please use https://github.com/EasyEngine/easyengine/discussions for support questions.

    If you feel the issue is a EasyEngine specific issue, please attach the output of the following commands.

    System Information

    Im trying to make a new web site and im encountering this error I tried using different domain but still getting same issue

    Reviewed by jpicao at 2022-01-24 16:32
BetterWPCLI - a small, zero-dependencies, PHP library that helps you build enterprise WordPress command-line applications.
BetterWPCLI - a small, zero-dependencies, PHP library that helps you build enterprise WordPress command-line applications.

BetterWPCLI - a small, zero-dependencies, PHP library that helps you build enterprise WordPress command-line applications.

May 3, 2022
A PHP Command Line tool that makes it easy to compile, concat, and minify front-end Javascript and CSS/SCSS dependencies.

Front End Compiler A PHP Command Line tool that makes it easy to compile, concat, and minify front-end Javascript and CSS/SCSS dependencies. The minif

Nov 12, 2021
Twitter raffles in the command line, with PHP and minicli
Twitter raffles in the command line, with PHP and minicli

Rafflebird Rafflebird is a highly experimental CLI application for giveaways / raffles on Twitter, built in PHP with Minicli. Disclaimer: The recent s

May 14, 2022
PHP Interminal is a command-line tool that gives you access to PHP Internals discussions in your terminal.
PHP Interminal is a command-line tool that gives you access to PHP Internals discussions in your terminal.

PHP Interminal is a command-line tool that gives you access to PHP Internals discussions in your terminal. ??

Dec 12, 2021
Console - The Console component eases the creation of beautiful and testable command line interfaces.

Console Component The Console component eases the creation of beautiful and testable command line interfaces. Sponsor The Console component for Symfon

May 25, 2022
Provides the equivalent of request ( Context ) and response ( Stdio ) objects for the command line interface

Provides the equivalent of request ( Context ) and response ( Stdio ) objects for the command line interface, including Getopt support, and an independent Help object for describing commands.

May 6, 2022
Lovely PHP wrapper for using the command-line

ShellWrap What is it? It's a beautiful way to use powerful Linux/Unix tools in PHP. Easily and logically pipe commands together, capture errors as PHP

May 3, 2022
A PHP library for command-line argument processing

GetOpt.PHP GetOpt.PHP is a library for command-line argument processing. It supports PHP version 5.4 and above. Releases For an overview of the releas

May 24, 2022
Patrol is an elegant command-line tool that keeps your PHP Project's dependencies in check.
Patrol is an elegant command-line tool that keeps your PHP Project's dependencies in check.

Patrol is an elegant command-line tool that keeps your PHP Project's dependencies in check. Installation / Usage Requires PHP 8.0+ First, install Patr

May 27, 2022
A PHP command line tool used to install shlink
A PHP command line tool used to install shlink

Shlink installer A PHP command line tool used to install shlink. Installation Install this tool using composer.

Jan 10, 2022
Generic PHP command line flags parse library
Generic PHP command line flags parse library

PHP Flag Generic PHP command line flags parse library Features Generic CLI options and arguments parser. Support set value data type(int,string,bool,a

Mar 2, 2022
A simple command-line tool whose aim is to facilitate the continous delivery of PHP apps
A simple command-line tool whose aim is to facilitate the continous delivery of PHP apps

Deployer Simple command-line tool that aims to facilitate the continous delivery of PHP apps, particularly Laravel apps. Imagine you want to update yo

Sep 8, 2021
🍃 In short, it's like Tailwind CSS, but for the PHP command-line applications.
🍃 In short, it's like Tailwind CSS, but for the PHP command-line applications.

Termwind Termwind allows you to build unique and beautiful PHP command-line applications, using the Tailwind CSS API. In short, it's like Tailwind CSS

May 27, 2022
php command line script to DCA crypto from Coinbase Pro

dca.php A simple php script designed to be run via the command line via a cron job. This will connect to coinbase pro and buy the crypto coins specifi

Oct 22, 2021
A PHP library for command-line argument processing

GetOpt.PHP GetOpt.PHP is a library for command-line argument processing. It supports PHP version 7.1 and above. Releases For an overview of the releas

May 20, 2022
Command-Line Interface tools

Aura.Cli Provides the equivalent of request ( Context ) and response ( Stdio ) objects for the command line interface, including Getopt support, and a

May 6, 2022
Another Command Line Argument Parser

Optparse — Another Command Line Argument Parser Install 1. Get composer. 2. Put this into your local composer.json: { "require": { "chh/optparse

Nov 1, 2019
👨🏻‍🚀 A command-line tool that gives you the Alpine Day 2021 schedule in your timezone. 🚀
👨🏻‍🚀 A command-line tool that gives you the Alpine Day 2021 schedule in your timezone. 🚀

Alpine Day Schedule a command-line tool that gives you the Alpine Day 2021 schedule in your timezone. ?? Quick start Requires PHP 7.4+ # First, instal

Jun 10, 2021
A command line code generator for Drupal.

Drupal Code Generator A command line code generator for Drupal. Installation Download the latest stable release of the code generator.

May 20, 2022