The Django installer




This installer uses Alpine, Linux and Python3 as the foundation of Django. If you need to add new packages or Linux Python3 libraries you can use the Extra packages and Django manage plugins.


How to use it

To use it you have to start a new project and select Django in the first selector. It produces a totally useful Django installation, with all the necessary packages and configurations. The app is prepared for its working in remote servers and in your local computer.

$ gorilla build my-project

Later, you’ll have to add the domain name.

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.

Your project folder will be like this:

  • .gorilla: is the folder  GorillaJS uses to save the project’s configuration. You shouldn’t access here.
  • logs: it has the exit “DEBUG” of the Django Logging module.
  • src: is the published folder of the project.
  • scr/testlocal: the main app name is produced automatically taking the domain name. In that case it’s test.local.
  • src/testlocal/requirements.txt: GorillaJS creates a requirements.txt file to manage python modules. GorillaJS installs it every time the project is built. (gorilla build)
  • src/testlocal/ this file is modified by GorillaJS every time the project is built to configure the data access to the database and the logging.


Next steps

The next step could be installing other database engine or creating a superuser to access to the admin. To do it you can use the Django manage and DB for Django plugins. With the first one you’ll be able to manage django-admin without needing to access to Docker container directly. With the second one you’ll be able to use PostgreSQL or MySQL in your project. 

Because of an implementation mistake of Gunicorn in GorillaJS isn’t possible to change the domain name of the project using the f command. If you have to change it you’ll have to create a new project.

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?