Save your changes for the next time




$ gorilla plugin add commit

To uninstall:

$ gorilla plugin remove commit


How to use it

This plugin allows you to save your project’s changes you had done on the Docker container. It doesn’t matter how did you do it or what did you use as tools to do it.

$ gorilla commit [container name | container id]

If you don’t pass the name or the id it will save on the main container of the app.

It’s important to make a difference between the command “commit” and Docker one’s. GorillaJS command is in charge of saving a reference in your project in order that the next time it starts, it uses the correct container instead of one who was automatically in the installer. Besides that, it does a container command like Docker would do.


Locate the container's name or id

To see the container’s name and id you can use ps Docker command.

$ docker ps

It will give you a list with all the containers.

GorillaJS uses as prefix the project domain name. Generally, projects use two containers: the main server for the app and the other for the database. If your project domain name was myproject.local and you were using a WordPress installer you would see in the list two containers called: myproject.local y myproject.local_mysql.

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?