This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
---------------------------------- Idea ------------------------------------------- | |
Cuando usamos la representación del lado del cliente en React(CSR) a través de | |
react-router-dom, lo que hacemos es simular un enrutamiento del lado del cliente. Esta | |
rutas virtuales son gestionadas por react-router para armar el path en la url del navegador. | |
Esto funciona muy bien en desarrollo. | |
-------------------------------- Problemática --------------------------------------- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
_______________________________ Server Compartido _______________________________----_- | |
En el gist anterior se muestra como alojar un app de React js en el root de la carpeta | |
public, pero en general queremos alojar multiples app en nuestro server. | |
Para esto debemos hacer algunas modificaciones en nuestra estructura. | |
La estructura anterior era: | |
server/ | |
|_ _ public_html | |
|_ _ .htaccess |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
____________::::::::::::::::::: Entornos de desarrollo :::::::::::::::::::________ | |
Cuando desarrollamos nuestras apps generalmente trabajamos con distintos entornos: | |
1. development | |
2. test | |
3. production | |
4. staging(opcional, pre production) | |
Teniendo en cuenta esto no queremos ensuciar la BD de production con las | |
pruebas de test ó development. Para esto es que hacemos uso de librerias |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
_________ ::::::: Exportación de variables leidas a partir de un archivo :::::::::: __________ | |
El primer escenario es el caso simple en el que exportamos un contenido de manera directa, | |
es decir, exportamos una variable que tiene como valort un string en linea. Esto lo podemos | |
hacer desde .bashrc || .bash_profile || /etc/environment || /etc/profile | |
Por ejemplo: | |
/etc/environment | |
MI_VARIABLE="https://dommain.com" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
------------- Hosting compartido a través de Nginx ------------- | |
---__________________________________________________________________--- | |
El objetivo será enlazar las distintas aplicaciones con un nombre específico dentro del dominio del servidor | |
compartido. Asumiendo que el dominio es "digitalservices.com" vamos a realizar la implementación tal que | |
tengamos el siguiente esquema: | |
____Esquema de APIS con Node JS | |
HOST | CNAME | SUBDOMAIN | DOMAIN | PATH | TIPO | PROJECT | PORT | ENDPOINT |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
------------- Partes de una URL ------------- | |
---__________________________________________________________________--- | |
Elementos de una URL | |
* Protocolo HTTPS | |
* Subdominio | |
* Dominio | |
* TLD | |
* Ruta |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
----- Preparación del serve Centos 7 con Apache httpd ---------- | |
---------__________________________________________________________________--------- | |
___Premisas para la puesta en producción | |
- Un hosting funcional con una MV de Centos 7(x64) acceso root | |
- Un DNS válido para poder enlazar a la IP del server | |
- Conocimientos básicos del shell de Unix | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-------- Hosting compartido a través de Apache Httpd ----------- | |
---__________________________________________________________________--- | |
El objetivo será enlazar las distintas aplicaciones con un nombre específico dentro del dominio del servidor | |
compartido. Asumiendo que el dominio es "digitalservices.com" vamos a realizar la implementación tal que | |
tengamos el siguiente esquema: | |
____Esquema de APIS con Node JS | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# root en este caso public_html/.htaccess | |
RewriteEngine on | |
RewriteCond %{HTTP_HOST} <IP_HOST> [NC] | |
RewriteCond %{REQUEST_URI} ^/$ | |
Rewriterule ^(.*)$ https://<IP_HOST>/tasks [L,R=301] | |
ErrorDocument 404 https://<IP_HOST>errors/404.html | |
ErrorDocument 500 https://<IP_HOST>/errors/500.html | |
# subdirectorios en este caso public_html/tasks/.htaccess |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ----------------------------- Creación de acceso Ubuntu Gnome ------------------------------- | | |
Para crear accesos directos en Ubuntu hay una forma sencilla de llegar al objetivo. | |
En un editor de texto colocamos las siguintes sentencias: | |
[Desktop Entry] | |
Type=Application | |
Categories=Utility | |
Name=Lapce | |
Icon=/home/juan/lapce/icons/lapce/lapce_icon.png |
OlderNewer