Devstack enable Nginx instead of using 'runserver' and Fullstack mysql workbench connection

[Tao]

Hi there,

      We have an open edx devstack instance up and running on our server and it works perfectly. I did some research about the devstack version and found it actually using 'runserver' or WSGI to run the studio or lms. I understand that devstack version is for development and full stack version is for production:

      Got it here:

          

• Simplifies certain production settings to make development more convenient. For example, it disables nginx and gunicorn in favor of runserver for Django development. LInk: https://openedx.atlassian.net/wiki/spaces/OpenOPS/pages/60227787/Running+Devstack

      I am wondering how to set up/ enable the nginx on edx devstack, is there anyone has some solutions or ideas about that?

      Second Question:   

             Also, I have a fullstack version running on my machine. I wonder if there is anyone could use the mysql workbench to connect to the database? I am not able to connect the database on fullstack as I did before on devstack. Here is the my configuration for fullstack:

       Here is the error message:

     

       Really appreciate if there are any suggestions and ideas! Thanks in advance

       

[Trinh Nguyen]

Hi,

1. Nginx: First thing, why Nginx on devstack? Is there any particular reason for that otherwise it's just not necessary. But if you want to try, just kill the runserver process and deploy the gunicorn, nginx yourself: check out here.

2. wrong key.

Trinh Nguyen | Founder & CTO

E: dangt...@gmail.com | W: www.edlab.xyz

--
You received this message because you are subscribed to the Google Groups "General Open edX discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/e75b6de3-b49b-4e50-9ea3-4d8b29589b0d%40googlegroups.com.

[Clinton Blackburn]

All of our images tagged with latest (e.g. edxops/ecommerce:latest) are built from Ansible. They already have nginx and gunicorn installed, but we don't use them since the images are primarily intended for development and nginx/gunicorn slowed development. You can see the pull request that made this change at https://github.com/edx/devstack/pull/81.

Some of the containers have a script call devstack.sh in the application directory (e.g. /edx/app/discovery/devstack.sh). Calling this script with the start parameter (e.g. ./devstack.sh start) will start supervisor, which is configured to run nginx and gunicorn. The template for this file is available at https://github.com/edx/configuration/blob/5417daace1207112cf598603d4c4751f091ec29d/playbooks/roles/edx_django_service/templates/edx/app/app/devstack.sh.j2.

As we said when we first launched Docker Devstack, it is only intended for development at this time. The images might work in a production-like environment, but that is not something we support at this time. Additionally, the images are quite insecure by default, so please do not use them in production prior to changing the security-related settings.

Clinton