TerraMA² - Instalação NGINX

Responsáveis: Gribeiro, Jean e Raphael Willian da Costa

Data: 20/06/2018

Site: ​https://www.nginx.com

Versão: 1.10.3

---

Tópicos

• Instalação
• Configuração
  • TerraMA²
  • E-Sensing
  • TerraAmazon

Instalação

Para instalar o NGINX na maquina Ubuntu 16.04 LTS utilize o comando:

sudo apt get install nginx

Configuração

Os arquivos globais de configuração do NGINX estão localizados na pasta /etc/nginx. Os arquivos locais que indicam o caminho de cada aplicações sobre um domínio específico estão localizados em /data/nginx. Os arquivos publicos estão localizados em /data/http

TerraMA²

Para configurar o NGINX para servir para o endereço do terrama2.dpi.inpe.br utilize os seguintes comandos:

Na pasta /etc/nginx/sites-enabled criar o arquivo terrama2-default com o seguinte conteúdo:

server {
  server_name http://terrama2.dpi.inpe.br;
  listen 59989;

  # Include below the applications files

  include /data/nginx/terrama2/*.conf;

  server_name _;

  # Don't include files beyond this line
}

Para criar configurações de rota sobre o dominio do terrama2.dpi.inpe.br, crie arquivos com a extensão .conf dentro de /data/nginx/terrama2.

Para criar o diretório publico do TerraMA² para disponibilizar os arquivos para serem baixados, utilize o comando:

nano /data/nginx/terrama2/public.conf 

location /pub/ {
  autoindex on;

  root /data/http;
}

location /terrama2q/situacao_atual/ {
  root /data/http;

  index index.html;
}

Para criar os sub projetos do TerraMA², crie arquivos com a extensão .conf dentro de /data/nginx/terrama2. Por exemplo:

Projeto Acre

sudo nano /data/nginx/terraama2/acre.conf

##########################################################################
#
# WebApp
#
##########################################################################

location /acre/adm {
  proxy_pass http://127.0.0.1:36002;

  include proxy_params;
}

location /acre/adm/socket.io {
  proxy_pass http://127.0.0.1:36002;
  include proxy_params;

  # Path rewriting
  rewrite ^/acre/adm/socket.io/?(.*) /socket.io/$1 break;
}

location /acre/adm/i18n {
  proxy_pass http://127.0.0.1:36002;
  include proxy_params;

  # Path rewriting
  rewrite ^/acre/adm/i18n/?(.*) /i18n/$1 break;
}

##########################################################################
#
# WebMonitor
#
##########################################################################

location /acre/monitor {
  proxy_pass http://127.0.0.1:36003;

  include proxy_params;
}

location /acre/monitor/socket.io {
  proxy_pass http://127.0.0.1:36003;
  include proxy_params;

  # Path rewriting
  rewrite ^/acre/monitor/socket.io/?(.*) /socket.io/$1 break;
}

location /acre/monitor/i18n {
  proxy_pass http://127.0.0.1:36003;
  include proxy_params;

  # Path rewriting
  rewrite ^/acre/monitor/i18n/?(.*) /i18n/$1 break;
}

##########################################################################
#
# GeoServer
#
##########################################################################

location /acre/geoserver {
  proxy_pass http://127.0.0.1:8082/acre/geoserver;
  include proxy_params;

  add_header Access-Control-Allow-Origin *;
}

E-Sensing

Para configurar o NGINX para servir para o endereço do esensing.dpi.inpe.br utilize os seguintes comandos:

Na pasta /etc/nginx/sites-enabled criar o arquivo esensing-default com o seguinte conteúdo:

server {
  server_name http://esensing.dpi.inpe.br;
  listen 59991;

  # Include below the applications files

  server_name _;

  location /wtss/ {
       rewrite /wtss/?(.*) /wtss/$1 break;
       proxy_pass http://150.163.2.191:7654;
       include proxy_params;
  }

  # Don't include files beyond this line
}

TerraAmazon

Para configurar o NGINX para servir para o endereço do terraamazon.dpi.inpe.br utilize os seguintes comandos:

Na pasta /etc/nginx/sites-enabled criar o arquivo terraamazon-default com o seguinte conteúdo:

server {
  server_name http://terraamazon.dpi.inpe.br;
  listen 59990;

  # Include below the applications files

  include /data/nginx/terraamazon/*.conf;

  server_name _;
}

Para criar configurações de rota sobre o dominio do terraamazon.dpi.inpe.br, crie arquivos com a extensão .conf dentro de /data/nginx/terrama2.

Para criar o diretório publico do TerraAmazon para disponibilizar os arquivos para serem baixados, utilize o comando:

nano /data/nginx/terraamazon/public.conf 

location /pub/ {
  autoindex on;

  rewrite ^/pub/?(.*) /$1 break;

  root /data/http/terraamazon/;
}

Para servir a aplicação Monitor do TerraAmazon, crie o arquivo:

sudo nano /data/nginx/terraamazon/terraamazon.conf

##########################################################################
#
# Monitor
#
##########################################################################

location / {
  proxy_pass http://127.0.0.1:8100;
  include proxy_params;
}

location /fip_cerrado {
  proxy_pass http://127.0.0.1:8091;

  include proxy_params;
}

location /fip_cerrado/socket.io {
  proxy_pass http://127.0.0.1:8091;
  include proxy_params;

  # Path rewriting
  rewrite ^/fip_cerrado/socket.io/?(.*) /socket.io/$1 break;
}

location /fip_cerrado/login {
  proxy_pass http://127.0.0.1:8092;

  include proxy_params;
}

location /fip_cerrado/login/socket.io {
  proxy_pass http://127.0.0.1:8092;
  include proxy_params;

  # Path rewriting
  rewrite ^/fip_cerrado/login/socket.io/?(.*) /socket.io/$1 break;
}

##########################################################################
#
# TerraAmazon Monitor
#
##########################################################################

location /fip_cerrado_dev {
  proxy_pass http://127.0.0.1:8094;

  include proxy_params;
}

location /fip_cerrado_dev/socket.io {
  proxy_pass http://127.0.0.1:8094;
  include proxy_params;

  # Path rewriting
  rewrite ^/fip_cerrado_dev/socket.io/?(.*) /socket.io/$1 break;
}

location /fip_cerrado_dev/login {
  proxy_pass http://127.0.0.1:8094;

  include proxy_params;
}

location /fip_cerrado_dev/login/socket.io {
  proxy_pass http://127.0.0.1:8094;
  include proxy_params;

  # Path rewriting
  rewrite ^/fip_cerrado_dev/login/socket.io/?(.*) /socket.io/$1 break;
}

location /fip_cerrado_geoserver {
  proxy_pass http://127.0.0.1:8097;

  include proxy_params;
}

Reinicie o servidor do NGINX após realizar essas configurações:

sudo service nginx restart