The WordPress installer



How to use it

This installer produces a WordPress project totally usefulness with all the libraries and configures you need to make the app works in a local or remote server. To use it you have to start a new project:

$ gorilla build my-project

And select WordPress in the first selector.

Later you’ll have to put the domain name and the basic credentials for the database.

If you use Mac or Linux, at the end of the process you might need your admin password to change some files. If you use Window, you might need to load the console session as admin.

In a few seconds you’ll be able to access to your project through the browser. You’ll find the WordPress files in the my-project/application folder.



When the projects is already created you can test that a new container is created for your app.

$docker ps

GorillaJS modifies the container’s name to use the domain name that you have chosen for your project, adding a prefix.

If your project uses the fool.local domain the container’s name of the app will be foo.local and the database one’s will be foo.local_mysql.



GorillaJS uses MariaDB as engine for databases. If you need to change something in the database you have two options: you either access to the Docker database container directly or you use some of this GorillaJS plugins: Adminer or DBManager.


Libraries installation

To install new php or system libraries, just like the database, you have two options: you either access to the Docker container directly or you use some of this GorillaJS plugins which make easier this task: Composer and PEAR or Extra packages.






The NodeJS installer

The NodeJS template that comes as a default in GorillaJS uses the Express.js framework to start a server and return a response. This is optional, and once the application is running we can eliminate this server and use the application in any other way.


Why do you need to free the port 80? Can you make your own installers? Can you use GorillaJS in a remote server?