DEV Community: Euda

¡Ayuda! Necesito una APP

Euda — Fri, 31 Mar 2023 00:50:18 +0000

Aplicaciones vs páginas web: por qué es importante customizar tu plataforma en base a las necesidades del negocio

Comunicar en la virtualidad

Las aplicaciones móviles, redes sociales y páginas web tienen un punto en común: son excelentes herramientas de comunicación. Sin embargo, hay algunas ventajas de las apps (aplicaciones móviles) que deberías tener en cuenta.

Como empresa, negocio o emprendimiento tenemos múltiples tipos de contenidos para comunicar: videos, eventos, imágenes, textos, audios. Por eso, trasladarlo a una plataforma que combina todos estos elementos en un solo canal es un gran beneficio.

Las aplicaciones pueden incluir archivos multimedia, textos, datos, realizar llamadas, brindar servicios de geolocalización y mucho más, sacándole provecho a las capacidades que ya vienen integradas en el teléfono. Hay quienes dicen que hoy en día el teléfono inteligente o smartphone es una extensión del propio cuerpo, por lo que, imaginemos toda tu información al alcance de todos, en la palma de la mano de a quien querés llegar.

“Sin apps, los teléfonos inteligentes y las tabletas serían como vehículos de sofisticados diseños, pero sin gasolina.”

La particularidad de esta herramienta, no es solamente la capacidad de contener varios formatos y tipos de archivos, sino también su versatilidad para un fácil acceso. Muchas empresas han querido aprovechar esta tecnología, en algunos casos, con suficiente éxito, como son los bancos e incluso instituciones estatales y gubernamentales. La virtualidad puede ser compleja, pero hay herramientas que nos acercan cada vez más: asistentes virtuales, chatbots, entre otras.

Oportunidades de negocio

Uber, Rappi, PedidosYa, Spotify, Brubank y más: todas aplicaciones que surgieron a partir de necesidades concretas. Los empresarios encontraron un nuevo nicho para explotar, y el acompañamiento de la tecnología fue clave para poder efectuarlo.

El e-commerce se encuentra en alza al punto que las tiendas físicas o retail en todo el mundo están buscando nuevas soluciones para mantenerse en pie. O por el contrario, nuevos negocios como showrooms o pequeños emprendimientos aparecen y se promocionan en redes, pero subsisten únicamente en lo digital.

Sin embargo, ya sea una plataforma para e-commerce, una plataforma para reservar turnos o gestionar paquetes y envíos, la mejor opción es una aplicación personalizada. Si bien las redes o páginas web -como TiendaNube, Wix, entre otras- son muy útiles para los negocios que están empezando, al momento de crecer es un beneficio tener el poder de customizar tu plataforma y no depender de las limitaciones de estos prestadores.

Al fin y al cabo, es el medio de contacto más importante con tus clientes. Si no tuviese una página web o aplicación propia, durante el apagón de Facebook, Instagram y Whatsapp muchas ventas cayeron y, más importante, se perdió la comunicación con el cliente.

PWA o Progressive Web Apps

Actualmente, hay muchas opciones a considerar, como una Progressive Web App o PWA, es decir, una aplicación web con características de aplicación. Es el híbrido perfecto entre una app y una página web: puede soportar las mismas funcionalidades que una aplicación -como, por ejemplo, realizar videollamadas, chats, geolocalización- desde una url para usar en cualquier navegador, tanto en el teléfono como en la computadora. Es fácilmente adaptable a todos los formatos y pantallas.

Entre las ventajas de esta solución, podemos mencionar:

No es necesario instalar una aplicación desde el Google Play o App Store, ya que funcionan en cualquier navegador como Chrome, Safari, Firefox, etc.
Puede funcionar sin conexión a internet, en algunos casos. Dependiendo de la funcionalidad que se le da, como una app, no es necesario que tenga conexión a internet para mostrar su contenido.
Permite enviar notificaciones push a los usuarios, sin que el usuario haya instalado una aplicación.

Asesorate SIN COSTO

Con tantas variables a tener en cuenta, un asesoramiento personalizado será siempre lo más valioso para que tu negocio crezca. Si te interesa escalar tu negocio no dudes en contactar una entrevista SIN COSTO con nosotros.

Y si todavía no me creés, mirá este caso de éxito dónde uno de nuestros clientes cuenta cómo lo ayudamos a escalar su negocio.

#EudaStyle, long-term quality

Euda — Tue, 21 Mar 2023 13:22:11 +0000

We build software with processes that help your digital project take off

Creating an app is a science that needs quality and precision. With more than 12 years of experience innovating, at Euda we use the same top-notch processes as other well-known tech giants. In this article, you’ll find what are the first-class technology and work processes that we use to develop our success stories’ apps.

There are a lot of things that can go wrong working in IT. For instance, a junior developer accidentally erases a whole production database of an e-commerce app and it affects not only the work of hundreds of people but the final customers. Or, maybe there is a bug that can stop the production of a whole factory, generating huge financial losses. Security is key and this is why we work in a way to ensure all these examples mentioned above never happen.

Cross-code control

Code review between cross-hierarchy teammates is one of the many actions taken to prevent this. Developers proofread each other’s lines of code before updating it on the system, checking each other’s code for mistakes.

Quality Assurance

Another important point is QA, with manual and automated testing. Most IT companies provide this service for their products. However, there are some key points to make it even better. For instance, automated tests should be integrated in the pipeline so that they run automatically with every deployment.

Regarding manual testing, although they may sound similar, there is a huge difference between a bug and a glitch. Bugs are usually coding errors, whereas glitches are errors that happen when the engine does not work as expected. Also, there are some metaapp features that may become bugs if the final users don’t like them. This is why our QA engineers always test with an open mind and anticipate both users’ moves and their expectations of the product.

Agile Methodologies

One may believe that organizing beforehand to achieve a perfectly calibrated work before starting any project allows us to accomplish better results. However, calibrating work such as an analogical clock may take too long. The formula used in our success stories involves bumpy starts and lots of refining later, and I believe that, in most cases, this is better than no starting at all. Refining tasks is the core of agile methodologies and combined with high quality processes is how we carry out extremely complicated projects at Euda.

We believe that organising work by following the agile methodologies principles is the way to go. Through our work we have come to value:

Individuals and interactions, over processes and tools
Working software, over comprehensive documentation
Customer collaboration, over contract negotiation
Responding to change, over following a plan
Find out more information on the Agile manifesto.

Multiple development environments

Moreover, safe and independent environments for development, testing and production ensure safety and quality at every step. Junior developers must learn from others and test in their own local environment and, again, before having access to production their code is reviewed by others.

Automation: continuous integration, delivery and deployment

And last but not least, we use tools such as Jenkins and Bitbucket Pipelines to ensure that the state of development is always available and transparent, and that a compiled application can be accessed at any time. That's how we focus on CI/CDD or Continuous Integration, Delivery and Deployment.

Following these principles, we had achieved digital projects’ scalability and product quality. It does not rely only on essentially big and complex teams. We believe that small but organised teams, added to all the good practises highlighted above are the best foundations for great software development.

Want to be our next success story? Visit our website to find out more and do not hesitate to contact us!

Redirect 301 con CloudFront y Lambda@EDGE

Euda — Tue, 21 Mar 2023 13:08:24 +0000

Hace poco tuve un requerimiento que consistía en redirigir una URL registrada en Route53 hacia una Progressive Web Application (PWA) deployada en un Bucket de S3 y distribuida a través de Cloudfront con subdominio propio.

Para mi sorpresa, AWS no puede realizar esa petición utilizando los servicios antes mencionados de una manera simple. En este artículo les voy a contar cómo hacerlo paso por paso.

¿Qué es un Código de estado de respuesta HTTP 301?

Existen diversos códigos de estado como respuesta a una petición HTTP, entre ellos el código 301, el cual indica un redireccionamiento permanente de una URL a otra, enviando a todos los usuarios a la nueva URL destino. Comúnmente se utiliza cuando cambiamos de URL una web ya existente.

Para más información, leer:

Códigos de estado de respuesta HTTP

Manos a la obra

Para realizar la redirección solicitada vamos a crear una función Lambda@EDGE que evalúe el host de un request y, si empata con la URL que queremos redirigir, realice un redirect 301 a la URL de nuestra PWA. Esa función vamos a asociarla a la distribución de CloudFront donde se encuentra la PWA.

Resumiendo, lo que hay que hacer es:

Ir a CloudFront y agregar nuestra URL, la que queremos redirigir, como un Alternative domain names. Para ello, nos dirigimos a nuestra distribución de CloudFront, en la pestaña general editamos los Settings y agregamos un Alternative domain name (CNAME) colocando la URL a la que vamos a aplicarle el Redirect 301.
Ahora tenemos que vincular nuestra URL a redirigir con la distribución de CloudFront. Para hacerlo, dirigirse a Route53, crear un record tipo A y colocar la misma URL que agregamos en el paso anterior. Vamos a filtrar la distribución de CloudFront buscándola por Alias y veremos que cuando seleccionemos CloudFront automáticamente nos va a aparecer la opción para elegir la distribución de nuestra PWA, gracias a que previamente agregamos ese dominio como Alternative domain name a nuestra distribución.
Por último, realizar un función lambda@EDGE y asociarla a nuestra distribución CloudFront para que cuando accedamos mediante la urlARedirigir realice una respuesta 301 y nos redirija a la URL original de la PWA. Para esto, vamos a ir a Lambda -> Create Function y elegimos Author from Scratch. Vamos a utilizar NodeJs y una arquitectura x86 para crear nuestra función.

Una vez creada la función nos va a salir un código de muestra, el cuál hay que editar y agregar el siguiente código:


exports.handler = async (event) => {
  const request = event.Records[0].cf.request;
  if (request.headers.host[0].value === 'urlARedirigir') {
    return {
      status: '301',
      statusDescription: `Redirecting to other domain`,
      headers: {
        location: [{
          key: 'Location',
          value: `https://urlPWA${request.uri}`
        }]
      }
    };
  }
  return request;
};

Un detalle importante respecto a la función es que urlARedirigir es solo el HOST de nuestra URL, por ende su valor NO debe contener el protocolo.
Ejemplo:
URL = https://exampleUrl.com
Host = exampleUrl.com

Luego de ingresar el código realizamos un deploy (presionando el botón ubicado arriba del cuadro de código) y debemos realizar una publicación de nuestra función Lambda desde el desplegable action -> publish new version.

Antes de continuar triggereando nuestra función con nuestra distribución de CloudFront, hay que ir a la solapa de Configuration y seleccionar Permission en la columna de la izquierda. Allí veremos que existe un ROLE creado. Clickeamos sobre el nombre del rol y nos va a dirigir al servicio de IAM.

Dentro del servicio de la configuración del ROL en el servicio de IAM nos dirigimos a la solapa de Permissions y editamos la Policy creada agregándole varios permisos, dejándola así:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "logs:CreateLogGroup",
            "Resource": "arn:aws:logs:us-east-1:<accountID>:*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "logs:CreateLogStream",
                "logs:PutLogEvents",
                "lambda:GetFunction",
                "lambda:EnableReplication*",
                "iam:CreateServiceLinkedRole",
                "cloudfront:UpdateDistribution",
                "cloudfront:CreateDistribution"
            ],
            "Resource": [
                "arn:aws:logs:us-east-1:<accountID>:log-group:/aws/lambda/redirect301:*",
                "arn:aws:cloudfront::<accountID>:distribution/*",
                "arn:aws:lambda:*:<accountID>:function:*",
                "arn:aws:iam::*:role/*"
            ]
        }
    ]
}

Luego, nos dirigimos a la solapa de Trust relationships, clickeamos el botón Edit trust relationship y editamos la policy para que quede de la siguiente manera:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": [
          "lambda.amazonaws.com",
          "edgelambda.amazonaws.com"
        ]
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

Una vez realizado este cambio volvemos al servicio de Lambda y vamos a nuestra función. Tocamos el botón Add trigger y seleccionamos el servicio de CloudFront. A continuación, tocamos el botón de Deploy to Lambda@Edge. Esto nos va a levantar un popup donde seleccionaremos la distribución de CloudFront donde se encuentra nuestra PWA, seleccionaremos Viewer request como evento de nuestra distribución y, por último, damos el check confirmando el deploy y presionamos “Deploy”.

Una vez deployado el trigger podemos observar que en nuestra pantalla de la función aparece el servicio de CLoudFront. Por último, si vamos a la sección de Behavior de nuestra distribución de CloudFront veremos que en la parte de Functions Associations se encuentra en el Viewer Request nuestro Lambda@Edge recién creado.

¡Y eso es todo!

Gracias por haber leído, espero que les sea útil. Pueden dejar sus dudas o comentarios abajo.

404 error: QA Analyst not found

Euda — Mon, 20 Mar 2023 21:38:08 +0000

Considering that most professions do not offer the opportunity to keep working remotely, people are starting to look for new career paths. What seems to be the easiest choice for those in need of a new beginning is becoming a QA Engineer, QA Analyst or software tester. How hard can it be for someone who uses technology on a daily basis to test apps?

The demand for IT specialists

As reported by the Bureau of Labor Statistics, the employment of IT professionals is expected to grow 13% between 2020 and 2030, surpassing the average growth for occupations. Such an accelerated pace is reasonable considering that computer and information technology jobs benefited from the pandemic due to the new norm of working remotely. In just a few weeks the great majority of employees were forced to adapt to this trend which now seems to keep growing even after offices start to reopen. Reaching higher levels of productivity, and saying goodbye to the dreaded commute are just a few of the advantages. To put it simply, these changes benefited those working in IT since companies adapted easily to a digital workplace by taking advantage of the already used technology -such as Slack, Drive and Google Meet- to communicate remotely. There are no obstacles for companies to follow through with the transition and to even stay remote indefinitely.

During the current pandemic, employees are rethinking their careers, a common pattern after life-changing events, and as already mentioned above, job opportunities for IT professionals are increasing. The information technology world seems to be the best possible solution with well-paid positions, significant growth opportunities and the chance to work remotely. Such abrupt change is not easy to accomplish but many have found the way to do it.

Quality Assurance

One way of getting into the tech industry is by becoming a software tester, a QA analyst or a QA engineer. Some may think it is the quickest and easiest way since testing comes hand in hand with career growth. The experience and apprehension provided by this opportunity to explore different angles of the software development process can be later applied to different positions, such as test automation engineer, product manager and even software developer.

Nowadays, with the countless online courses anyone can become a software tester -at least an average one- and with this solid foundation, companies may hire you in view of the increasing worldwide demand.

The complexity of testing

Quality Assurance testers are responsible for testing websites or apps in order to find malfunctions or defects, a simple look at the app is not enough. The job consists of comprehensive and thorough tests, which are crucial. After all, it eliminates risks from the release process so companies can focus on their growth.

Knowing the responsibilities of a QA tester, it is important to understand the skills needed which most online courses tend to omit. First of all, good communication skills are essential, both written and verbal. Testers find themselves documenting use cases and bug reports that must be detailed and easy for the whole team to understand. For instance, developers should not have to ask for more detailed information once they read a bug report, and new employees should be able to become acquainted with a project by reading the use cases. To ensure well-detailed documentation, a tester needs to have a clear idea of UI/UX terminology and behavior driven development (or BDD).

Furthermore, as some may believe, using a phone or computer on a daily basis should be enough expertise for the job. However, this could not be further from the truth. A tester must have a broad range of knowledge in software applications, hardware, cloud computing and networks. This includes, for example, understanding the difference between desktop and mobile operating systems, such as Windows, MacOS, Linux, IOS and Android. With the increasing competition in the browser market, new features are added or refined with the intention to differentiate themselves. Consequently, the outcome of a project may vary depending on which browser is used. Therefore, testers need to assure the quality and accessibility of a software in every OS since no one can predict how an user chooses to interact with it.

Finally, a software tester must familiarize with all the tools used in IT jobs. Starting with a solid understanding of agile methodologies for team collaboration and knowledge of the most popular kanban boards to report bugs and organize work, such as Trello, Jira or Asana, frequently asked in IT hiring processes. Followed by database management systems, for instance, MongoDB Compass, MySQL and phpMyAdmin. In addition, the proficiency in automation tools is valuable: Cucumber with Appium or Selenium for those more advanced or TestProject for beginners. For writing test cases, TestRail is one that might come in handy, and Postman for API testing.

Even though learning manual QA can be fast, easy and affordable for those seeking a change in their profession, only those eager to learn, ready to persistently build on their skill set, and those who have the aspiration to become an expert at the job will make it. The demand for QA testers is growing but there are not enough qualified people to fill these positions since it takes time and resources to build on the skill.

If you think you got what it takes to become part of the Euda QA team, do not hesitate to contact us! Good luck!

Please comment below on some related topics that you would like to read more about.

#EudaStyle, long-term quality

Euda — Wed, 11 May 2022 20:27:07 +0000

We build software with processes that help your digital project take off

For us, creating an app is a science that needs quality and precision. With more than 12 years of experience innovating, at Euda we use the same top-notch processes as other well-known tech giants. In this article, you’ll find what are the work processes that we use to develop our success stories’ apps. Our goal is that, maybe, you can get some inspiration for your own!

There are a lot of things that can go wrong working in IT. For instance, a junior developer accidentally erases a whole production database of an e-commerce app and it affects not only the work of hundreds of people but the final customers. Or, maybe there is a bug that can stop the production of a whole factory, generating huge financial losses. Security is key and this is why we work in a way to ensure all these examples mentioned above never happen.

Code review between cross-hierarchy teammates is one of the many actions taken to prevent this. Developers proofread each other’s lines of code before updating it on the system, checking each other’s code for mistakes.

Another important point is QA, with manual and automated testing. Most IT companies provide this service for their products. However, there are some key points to make it even better. For instance, automated tests should be integrated in the pipeline so that they run automatically with every deployment.

One may believe that organizing beforehand to achieve a perfectly calibrated work before starting any project allows us to accomplish better results. However, calibrating work such as an analogical clock may take too long. The formula used in our success stories involves bumpy starts and lots of refining later, and we believe that, in most cases, this is better than no starting at all. Refining tasks is the core of agile methodologies and combined with high quality processes is how we carry out extremely complicated projects at Euda.

We believe that organising work by following the agile methodologies principles is the way to go. Through our work we have come to value:

Individuals and interactions, over processes and tools
Working software, over comprehensive documentation
Customer collaboration, over contract negotiation
Responding to change, over following a plan
Find out more information on the Agile manifesto: https://agilemanifesto.org/

Finally, safe and independent environments for development, testing and production ensure safety and quality at every step. Junior developers must learn from others and test in their own local environment and, again, before having access to production their code is reviewed by others.

Following these principles, we had achieved digital projects’ scalability and product quality. It does not rely only on essentially big and complex teams. we believe that small but organised teams, added to all the good practises highlighted above are the best foundations for great software development. That's why we encourage you to follow this principles. Good luck!

Want to be our next success story? Visit our website to find out more and do not hesitate to contact us!

#EudaStyle, calidad a largo plazo

Euda — Tue, 25 Jan 2022 18:55:02 +0000

Hay muchas cosas que pueden salir mal trabajando en sistemas. Por ejemplo, un desarrollador junior borra accidentalmente la base de datos de producción completa de una aplicación de e-commerce y afecta no solo el trabajo de cientos de personas sino también a los clientes finales. O tal vez haya un error que pueda detener la producción de toda una fábrica generando enormes pérdidas financieras. La seguridad es clave y es por eso que en Euda trabajamos para garantizar que estos ejemplos mencionados anteriormente nunca sucedan.

La revisión de código entre compañeros de equipo de jerarquía cruzada es una de las muchas acciones que se toman para evitar esto. Otros analistas desarrolladores o incluso líderes de proyecto revisan las líneas de código de los demás antes de actualizarlo en el sistema, verificando el código de los demás en busca de errores.

Otro punto importante es el control de calidad con pruebas manuales y automatizadas. La mayoría de las empresas de IT brindan este servicio para sus productos. Sin embargo, hay algunos puntos clave para mejorarlo aún más. Por ejemplo, las pruebas automatizadas deben integrarse en el pipeline de buildeo para que se ejecuten automáticamente con cada implementación.

Con respecto a las pruebas manuales, los errores o bugs más comunes que aparecen pueden ser tanto errores de codificación, como fallos que se dan cuando el sistema no funciona como se esperaba. Además, hay algunas características de la aplicación que pueden convertirse en errores si a los usuarios finales no les gustan. Nuestros ingenieros de control de calidad (equipo de QA) siempre prueban con una mente abierta y anticipan tanto los movimientos de los usuarios como sus expectativas del producto.

Organizarnos de antemano para lograr un trabajo perfectamente calibrado antes de iniciar cualquier proyecto nos permite lograr mejores resultados. Sin embargo, el trabajo de calibración para que todo funcione como un reloj analógico, puede llevar demasiado tiempo. La fórmula utilizada en nuestras historias de éxito implica comienzos con baches y mucho refinamiento más adelante, y creo que, en la mayoría de los casos, esto es mejor que no comenzar en absoluto. El refinamiento de tareas es el núcleo de las metodologías ágiles y combinado con procesos de alta calidad es como llevamos a cabo proyectos extremadamente complicados en Euda.

Creemos que organizar el trabajo siguiendo los principios de las metodologías ágiles es el camino a seguir. A través de nuestro trabajo hemos llegado a valorar:

Individuos e interacciones, sobre procesos y herramientas.
Software funcionando, sobre documentación exhaustiva.
Colaboración con el cliente, sobre negociación contractual.
Respuesta ante el cambio, sobre seguir un plan.

Para más información sobre el manifiesto Agile consulte aquí.

Por último, los entornos seguros e independientes son clave para asegurar un software de calidad. Trabajamos en un entorno de desarrollo (“dev”), que es un entorno inestable donde los analistas programadores trabajan directamente, un entorno de prueba (“test”), donde se corren todas las pruebas de calidad, y finalmente el entorno de producción (“prod”), que es el entorno estable al que los usuarios finales tienen acceso.

Los desarrolladores junior deben aprender de otros y probar en su propio entorno local y, como mencionamos más arriba, otros colaboradores revisan su código antes de volcar su desarrollo en el entorno de producción.

Siguiendo estos principios, logramos la escalabilidad de los proyectos digitales y la calidad del producto. No depende solo esencialmente de equipos grandes y complejos. Creemos que los equipos más chicos, pero organizados sumados a todas las buenas prácticas destacadas anteriormente, son la mejor base para un gran desarrollo de software.

¿Quieres ser nuestro próximo caso de éxito? Visitá nuestro sitio web para obtener más información y no dudes en ponerte en contacto con nosotros.

Sails development with Docker and Docker Compose

Euda — Wed, 14 Apr 2021 14:18:32 +0000

Docker makes it easy to set up and run a development environment and also simplifies the deployment of your applications. In this article we will see how to setup a Sails development workflow with Docker and Docker Compose.

Whats and whys: Docker & Docker Compose

The goal of this article is to make setting up a Docker workflow for Sails as simple as possible. Docker makes it easier to set up and run a development environment and also simplifies the deployment.

First, we’ll get into how Docker and Docker Compose work and its benefits. Then a step by step guide to make our beloved Sails run inside a Docker container. Let's get started!

Containerization

Before talking about Docker and Sails we need to understand what is containerization and why we want it.
Containerization is a form of virtualization, through which applications are run in isolated user spaces called containers. We can think of a container as a lightweight virtual machine (but to be clear, it is not).

Comparing Containers and Virtual Machines [1]

But, why do we want it?

With containerization, everything an application needs to run, let's say, its binaries, libraries, configuration files and dependencies, are encapsulated and isolated in its container. This makes it easier to set up and run a development environment, and also simplifies the deployment by reducing the chances of missing or different versions of libraries, files or dependencies errors.

The container itself is abstracted away from the host OS, with only limited access to underlying resources. Isolation has its advantages, for example portability, stability and security.

So, standard, lightweight, secure… yes as developers we want containerization!

Docker and Docker Compose

The word "Docker" refers to several things including an open source project, tools and a company (Docker Inc., the company that primarily supports the project and tools).

Talking about the tools, Docker is a tool designed to make it easier to create, deploy, and run applications by using containers.

Container orchestration automates the deployment, management, scaling, and networking of containers. It can help you deploy the same application across different environments without needing to redesign it. As an example, microservices in containers make it easy to orchestrate services, including storage, networking, and security. Docker Compose is an orchestration tool for Docker containers. [2]

Installing Docker

Mac: https://docs.docker.com/docker-for-mac/install/
Windows: https://docs.docker.com/docker-for-windows/install/
Ubuntu: https://docs.docker.com/engine/install/ubuntu/
Others: https://docs.docker.com/engine/install/

Sails containerization

Now, how do we make Sails, our beloved Node framework, run inside a container?

Sails CLI image

Our container needs an image to run. Let's create one.
To do so, create docker-sails-cli directory and a file named Dockerfile inside it with this content:

FROM node:lts

RUN npm install -g sails@1.4.2

The FROM statement declares we are using node latest lts version as base image for ours. The syntax used is imageName:tag, if no tag is specified, the default is used. [3]

At the same time Node lts image is based on Debian Streatch. So this is our project environment, Sails 1.4.2, node 14.15.4 (at the time of writing this) running on a Debian Streatch.

Now we need to build our image.

docker build . -t sails-cli:1.4.2

Simple, right?

Let’s see what we did.

docker build [context] -t [tag]

context: The context where we are building. As we are in the same directory as the Dockerfile we use .. And also, there’s no need to specify the file name as Dockerfile is the default one.

tag: It is optional, but we want to tag the image we just built as we are probably going to have many different images with different versions for different projects.

Creating a new Sails project

Once we have our Sails CLI image built we are going to use it to create a new Sails project.

docker run --rm -v `pwd`:/app -w /app sails-cli:1.4.0 sails new sails-docker-example --no-frontend

docker run: Create and run a new container
--rm: Remove container after process finishes as we don’t need the container after that
-v: Mount current working directory (in our host computer) in /app path inside container. As a result we are sharing current directory with the container
-w: Set container current working directory to /app
sails-cli:1.4.0: Our previously built Sails image

sails new sails-docker-example --no-frontend: Sails CLI command we want to run in the container.

As a result, after running sails new in the container, we are going to find a new directory created with our new Sails project.

Now, let’s run our project:

cd sails-docker-example
docker run --rm -it -v `pwd`:/app -w /app -p 1337:1337 sails-cli:1.4.0 sails lift

-i: Keep STDIN open even if not attached
-t: Allocate a pseudo-TTY
-p: Maps container 1337 to host computer so we can reach our app through localhost:1337

It's alive!

Running and debugging

As you may notice, although our project is running, if you modify a file you will need to stop the container and launch it again to get the changes applied.

Nodemon to the rescue!

docker run --rm -v `pwd`:/app -w /app sails-cli:1.4.0 npm install nodemon --save-dev

Now, open package.json and in the scripts section add a new one, debug:

"scripts": {
    "debug": "nodemon --inspect=0.0.0.0 app.js",
    "start": "NODE_ENV=production node app.js",
...

And run again, but this time instead of sails lift we are going to run with npm:

docker run --rm -v `pwd`:/app -w /app -p 1337:1337 -p 9229:9229 sails-cli:1.4.0 npm run debug

Now, modify a file, save it and verify that the project is restarted automatically.

Finally, as we are running inside a container we need a way to get the debugger connected to the process, so we are mapping the 9559 port.

If you use VS Code you can use the following configuration in the
launch.json file:

{
    "version": "0.2.0",
    "configurations": [
        {
            "address": "localhost",
            "localRoot": "${workspaceFolder}",
            "name": "Attach to Remote",
            "port": 9229,
            "remoteRoot": "/app",
            "request": "attach",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "type": "node",
            "restart": true
        }
    ]
}

Docker compose

As we mentioned before Docker Compose is an orchestration tool. Compose allows us to define our infrastructure, let’s say, services, networks, volumes in an YAML file.

As a first step we will create a very simple file defining our Sails service on it. For this service we will set image, command, ports mapping, volume mounts, working directory, etc, as we did with Docker command line tool.

Our docker-compose.yml:

version: '3'

services:
    api:
        image: sails-cli:1.4.0 # same as with docker cli
        # Run npm install before starting sails to keep our dependencies installed and updated
        command: sh -c "npm install && npm run debug"
        working_dir: /app # same as -w with docker cli
        ports: # same as -p with docker cli
            - '1337:1337'
            - '9229:9229'
        volumes: # same as -v with docker cli
            - .:/app

Then, we will use docker-compose command to lift our service.

docker-compose up

The result is the same as running with Docker CLI.

In case we want to remove the created infrastructure, once stopped, run:

docker-compose down

This will remove all the containers, networks, volumes created with docker-compose up.

Database containerization

In most cases we will require a database for our project. In this example we will be using MongoDB but it’s possible to do the same with other db engine supported by Sails. [4]

For those who don’t know, MongoDB is a free and open-source cross-platform document-oriented database program. [5]

Fortunately MongoDB has an official image that we will be using to add a database service to our project.

First, we need to add Sails MongoDB adapter to our project. As we did before, we can add and install a dependency to our project with Docker like this:

docker run --rm -v `pwd`:/app -w /app sails-cli:1.4.0 npm install sails-mongo

Then, modify our project config and set mongo as our default adapter.

In the config/datastore.js file:

.
.
.

default: {
    adapter: require('sails-mongo'),
    url: process.env.DB_URL
},

Next we need to add MongoDB service to our docker-compose.yml and provision Sails service with needed config.

docker-compose.yml

version: '3'

services:
    api:
        image: sails-cli:1.4.0
        command: sh -c "npm install && npm run debug"
        working_dir: /app
        ports:
            - '1337:1337'
            - '9229:9229'
        volumes:
            - .:/app
        env_file:
          - ./sails.env # set env vars using a file

    db:
        container_name: mongodb # set name to the container
        image: mongo:4.4 # as of this writing, the latest version is 4.4.3
        volumes:
            - ./mongo:/data/db

We added a db service to our compose file, and also set an env file to Sails service. We will use that file to config our database connection.

sails.env

DB_URL=mongodb://root:@mongodb:27017/sails

Compose allows us to connect to db using the container name as network address, that is why we can use mongodb as the address in our connection url.

Important note: we are not enabling MongoDB authentication for this example but it is a good idea to do so for production environments. [6]

Finally, use docker-compose up to run, you will see MongoDB output along with Sails.

And we are done, a fully Sails development environment running on Docker!

Thank you so much for reading my post, comments are welcome!

Here is the link to the writter's twitter @vidueirof for any questions you may have.

[1] https://www.docker.com/resources/what-container
[2] https://www.docker.com/why-docker
[3] https://hub.docker.com/_/node
[4] https://sailsjs.com/documentation/concepts/extending-sails/adapters/available-adapters
[5] https://www.mongodb.com
[6] https://hub.docker.com/_/mongo

Certificación de dominio con Let’s Encrypt, NGINX y Docker Compose

Euda — Thu, 03 Sep 2020 20:24:23 +0000

Algunas definiciones

¿Qué es un Certificado SSL?

Un certificado SSL es un tipo de certificado digital que proporciona autenticación para un sitio web y habilita una conexión encriptada. Estos certificados comunican al cliente que el host del servicio web demostró la propiedad del dominio a la autoridad de certificación en el momento de la emisión del certificado.

SSL (Secure Socket Layer) es un protocolo de seguridad que encripta el envío y recepción de información entre el servidor y el cliente. Este crea una capa de conexión segura entre el navegador y el servidor del sitio web al que el usuario se conecta. Cualquier información que pase a través de esta capa está encriptada y es descifrada cuando llega a su destino.

Let’s Encrypt

Let's Encrypt es una autoridad de certificación (también conocidas como AC o CA por sus siglas en inglés) gratuita, automatizada, y abierta, que existe para el beneficio del público. Es un servicio provisto por el Internet Security Research Group o ISRG.

Certbot

Cerbot es un cliente extensible con todas las funciones para Let’s Encrypt CA, o cualquier otra autoridad de certificación que se comunique a través del protocolo ACME, capaz de automatizar las tareas de obtener certificados y configurar servidores web para usarlos.

Nginx

NGINX es un servidor web/proxy inverso ligero de alto rendimiento y un proxy para protocolos de correo electrónico.

Cómo certificar

Pre-Requisitos

Dominio registrado
Docker Compose instalado

Compose es una herramienta para definir y ejecutar aplicaciones Docker de varios contenedores. Se usa un archivo YAML para configurar los servicios de tu aplicación y luego, con un solo comando, crea e inicia todos los servicios desde tu configuración.

Pasos

1. Lo primero que haremos es crear los directorios donde Certbot alojará la configuración de los certificados y donde pondremos la configuración de nuestro servidor Nginx:

data/certbot/www/.well-known

Es muy importante que esté creado el directorio .well-known ya que en el mismo se guardará el challenge que Let’s encrypt utiliza para corroborar que tenemos control sobre el dominio. Es útil conocer los diferentes tipos de challenges que existen para elegir el más adecuado según el caso, es decir, el tipo de validación que Let’s Encrypt utiliza para verificar el control sobre el dominio.

2. Luego, crearemos el archivo de configuración de Nginx dentro del directorio recién creado, con el siguiente contenido:

server {
  listen 80;
  server_name NOMBRE_DEL_HOST;
  location / {
    return 301 https:// NOMBRE_DEL_HOST;
  }
  location /.well-known/acme-challenge/ {
    root /var/www/certbot;
  }
}
server {
  listen 443 ssl;
  server_name NOMBRE_DEL_HOST;
  location / {
    proxy_pass http://NOMBRE_DEL_HOST;
  }
  ssl_certificate /etc/letsencrypt/live/NOMBRE_DEL_HOST/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/NOMBRE_DEL_HOST/privkey.pem;
  include /etc/letsencrypt/options-ssl-nginx.conf;
  ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
}

El archivo de configuración deberá estar en dicho directorio:
data/nginx/web.conf

3. Una vez listo, pasaremos a crear el Compose que vamos a utilizar:

version: "3"
services:
  nginx:
     image: nginx:1.15-alpine
     ports:
       - "80:80"
       - "443:443"
     volumes:
       - ./data/nginx:/etc/nginx/conf.d
       - ./data/certbot/conf:/etc/letsencrypt
       - ./data/certbot/www:/var/www/certbot
     command: "/bin/sh -c 'while :; do sleep 6h & wait $${!}; nginx -s reload; done & nginx -g \"daemon off;\"'"

  certbot:
     image: certbot/certbot
     volumes:
       - ./data/certbot/conf:/etc/letsencrypt
       - ./data/certbot/www:/var/www/certbot
     entrypoint: "/bin/sh -c 'trap exit TERM; while :; do certbot renew; sleep 12h & wait $${!}; done;'"

Creado el Compose, no lo ejecutaremos, porque fallará la creación del Nginx debido a que no se encuentra creado el certificado que declaramos anteriormente en el archivo de configuración de Nginx.

Vamos a explicar un poco lo que hicimos en ese Compose: cruzamos datos entre Certbot y Nginx mediante los directorios creados anteriormente. Esto se debe a que necesitamos que el contenedor Nginx pueda acceder a los certificados y el challenge creados por el contenedor de Certbot.

En el contenedor de Certbot agregamos un entrypoint el cual verifica cada 12 horas si se puede renovar el certificado.

Por su parte, en el contenedor de Nginx agregamos un command el cual permite iniciar Nginx en primer plano y recarga su configuración y certificados cada 6 horas en segundo plano, asegurando que siempre tenga los nuevos certificados que se generen.

4. Finalmente, debemos crear el siguiente script cambiando los valores de domains y email:

El script debe estar en el mismo directorio donde se encuentra el docker-compose y el directorio data que creamos anteriormente. Vamos a darle permiso de ejecución al script y luego ejecutarlo:

chmod +x init-letsencrypt.sh 
sudo ./init-letsencrypt.sh

Como dijimos anteriormente, si queremos utilizar el comando docker-compose upno funcionará porque no se encuentran creados los certificados que seteamos en la configuración de Nginx. Ahí es donde entra en juego el script. Este script lo que hace es crear certificados dummies utilizando el contenedor de Certbot, para poder inicializar el contenedor de Nginx sin errores. Luego de que el contenedor esté inicializado, elimina los certificados dummies, le pide a Let’sEncrypt certificados para nuestro dominio y reinicia la configuración del contenedor de Nginx para recargar los certificados válidos. De este modo, no va a ser necesario utilizar dicho comando.

Si al ejecutar el script falla la creación de los certificados, es muy importante que lean y resuelvan el inconveniente antes de volver a ejecutarlo, ya que Let’sEncrypt bloqueará el dominio si hacen más de 5 intentos fallidos.

Por último, cabe aclarar que en este artículo tomamos información de varias fuentes, recopilando aquellas más completas para que este paso a paso resulte más fácil y práctico. Espero que les sea útil y cualquier consulta no duden en dejarla en los comentarios.

Para más info sobre este tema recomendamos nuestra nota en Medium:

Certificación de dominio con Let’s Encrypt, NGINX y Docker Compose | by Matias Quintana | Euda | Medium

Matias Quintana ・ Sep 3, 2020 ・
Medium

¡Muchos éxitos!

Development & Operations

Euda — Mon, 29 Jun 2020 17:56:52 +0000

A short and quick guide to dive into the DevOps world.

In this post I'll tell you what does it mean to be a DevOps engineer in a software factory, how to build the structure to support any app development and, finally, some recommendations and good practices to become a pro.

My work as DevOps

The DevOps engineer is in charge of implementing best practices to integrate development (Dev) and operations (Ops) by accelerating deliveries through automation, collaboration and iterative improvement and achieving a more efficient way of working throughout the development life cycle.

My work as DevOps engineer in the company involves infrastructure configuration and maintenance tasks, as well as automation of different projects' workflows and the construction of software life cycles, based on CI / CD with AWS, Digital Ocean, Bitbucket Pipelines and Jenkins. In addition to automating and streamlining the procedures and processes of software development, I am also responsible for maintaining implementation and monitoring tools.

Specializing in DevOps can help you target a growing working market with great opportunities.

Where to start

Continuous integration servers, containers and tools. These are the three legs needed to structure any development. AWS, Digital Ocean, Docker and Jenkins are the ones we choose. For starters, I recommend using Docker, Jenkins, and any server you have access to, like AWS or Digital Ocean.

What is Docker?

It's a container management service that allows developers to create applications, ship them to containers, and run them anywhere. Thus, it allows you to create your own custom environments that can include a variety of operating systems and development frameworks.

Docker containers are quite light and can be deployed on any physical and virtual machine, even in the cloud. To deepen about this tool, I recommend you read another of our articles with everything you need to know about Docker:

Everything you need to know about Docker | by Euda | Euda | Medium

Euda ・ Oct 16, 2019 ・
Medium

What is Jenkins?

Jenkins is an open source, java-based tool that enables CI / CD streams. It is one of the most used at present since, through plugins, it has a wide integrity with different tools (GIT - Nexus - Database - AWS - Azure - etc.). For large developments that require complex architecture, Jenkins has the ability to connect to different environments and orchestrate the development life cycle.

Good practices and recommendations

As in all tasks, there are good practices to follow. In my opinion, all DevOps engineers should:

Work together with the different areas / teams to find out their needs. These are the foundation of every DevOps task.
Know different tools, their strengths and weaknesses, and keep updated on them. Here you can see a periodic table with all the available DevOps' tools, each one has some info so that you can choose the most convenient for your project.

Do not always apply the same formula to all projects. In any development company there usually are several projects and teams working simultaneously. Not all projects are the same, so it's important to be in contact with all of them to carry out an analysis of each particular project, taking into account its scalability to use the appropriate tools.
Automate everything you can reducing times and errors that can be made in manual implementations.
Do not uphold the implementation done. Constant monitoring, analyzing logs, metrics or developers feedback are always necessary to make improvements to the flow.

What differentiates a Junior DevOps from a Senior?

In essence, a senior DevOps engineer analyzes any given problem holistically and trying to understand how changes can be made at an enterprise level, and not simply trying to solve the given problem one time. Frankly, this skill is less technical and more about evaluating and solving problems.

To have a deeper understanding of everything that needs to be learned to become a complete DevOps, you can see here a roadmap with the languages and programs that are recommended take into account. Nothing is accomplished overnight. There is a lot of information available so it's useful to get organized and learn little by little.

On the other hand, the article below is very complete and interesting to delve into the subject. It's based on the same roadmap shared above but with extra suggestions and courses' links:

The 2023 DevOps RoadMap | Javarevisited

javinpaul ・ Apr 30, 2024 ・
Medium

To finish, if your are ready, here are 10 online courses to start or keep learning. Thanks for reading till the end! I hope you found this useful and any questions you may have do not hesitate to comment.

Working from home during lockdown

Euda — Wed, 10 Jun 2020 15:19:30 +0000

Several months have passed and for those of us who work on IT, we will surely have to work from home for a while longer. It is likely that you have already adapted to remote work, however, it never hurts to review some tips for working remotely, being more productive and feeling better both at work and on a daily basis.

Manage times and spaces

The first #Eudatip to work from home in quarantine is to plan a routine that includes breaks at limited hours. This can be based on meals, for example, it's important to plan breakfast, lunch and snacks so that they are always at the same time, and avoid eating in front of the computer! Try to make the work and rest spaces different so that the rest becomes more effective.

Sometimes the comfort of the home can backfire. If you don't have colleagues or partners around you, it's easy to get distracted. There are always other things to do, like doing laundry, dishes, etc. Therefore, you have to do your best to put them on pause until finish or do them during breaks. Setting an alarm on your phone or computer can help you organize better.

Another tip is to get up and put on an outfit different from the one you wear to sleep. It can be other pajamas, more comfortable pants, whatever you want! The goal is to start the day with renewed energies.

Do not lose communication

Keeping fluid contact with your team is vital. Here are some tools and tips that we apply as a company and may help you:

Slack or any messaging tool of your choice. Communication is very important when you work remotely, especially because if you are not there, your team may forget about you. It is important that they know that you are available so that they can contact you. At Eudaimonia every day we greet each other with a “Good day” in the main channel and we say goodbye when our schedule ends.
Google Hangouts / Meet, if you have a business Gsuite, Zoom or other video conferencing apps. In this context, meetings are more important than ever. I'm not saying that several calls are necessary per day or per topic, especially when some issues can usually be solved with just an email. But the meetings that have already been set, daily if possible, must be an opportunity to take advantage of. It works to write down everything you did the day before so that you can share it at the meeting and that everyone is aware of the progress each one made.
A Kanban, to sort the tasks and priorities of each project. If you do not have a defined work plan from the beginning, it is best that as you begin to have requirements to write them in a Kanban. Trello is a very helpful tool, because it allows you to have visibility of what everyone is doing and measure the progress of each project.
Online news portals to keep you informed. Reading the news every day before starting helps us not to lose communication with the outside world and can be used to share interesting articles with your colleagues and generate conversation.

Knowing when and how to stop

This is one of the most difficult things since sometimes we just get carried away and work more than our stipulated time. Chances are that whatever you're doing after 12–13 hours of continuous work won't be the best quality, plus you'll be overloading yourself for the next day. Working remotely could make some people assume that you are available at any time of the day, but you are not.

On the other hand, a good tip is to end the day with a little exercise. If we jump directly from screen to screen, our eyes get tired and can cause headaches. If you do not like to exercise, with some spinal stretching that you can easily find on youtube is more than enough. There are no excuses! You can find short routines of up to 7 minutes. You'll feel less contracted and in a better mood.

To sum up, we know that working from home has its pros and cons, but the key is to keep trying until you find out what works best. Once you do, you're probably going to be able to work wherever you want. After a while you will realize that you can be much more productive than you thought.

Have you already put into practice any of these tips? Do you have any to add? Tell us in the comments below.

📌📌ATENCIÓN: OFERTA LABORAL📌📌

Euda — Fri, 13 Mar 2020 14:48:49 +0000

En Eudaimonia nos encontramos en la búsqueda de los siguientes perfiles:

-iOS Dev
-Android Dev
-Fullstack Dev

📌¿Qué ofrecemos?

✅Flex Time ⏱
✅Home Office🏡
✅Almuerzo los Viernes 🍝
✅Capacitaciones

¿Remuneración? La que nos digas en base a tu experiencia y conocimiento.

📍Palermo, Capital Federal, Buenos Aires, Argentina.

Si estas interesado/a y cumplís con los requisitos, enviá tu CV indicando puesto, remuneración pretendida y seniority a micaelaj@eudaimonia.com.ar

Más información en https://www.eudaimonia.com.ar

Improve your performance with Scrum Methodology

Euda — Fri, 24 Jan 2020 17:00:54 +0000

Learn how to incorporate this agile methodology to enhance your work performance. Here are some popular tools and recommendations for integrating agile philosophies' elements into your work.

Scrum methodology can help either large or small teams to achieve their work goals, satisfy their clients and develop a better team relationship. But, how?

First of all, let's review what Scrum is.

Born for software development, Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. This means, usable and worthy products, in which progress is acknowledgeable. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

How does it work? Easy. You probably already apply scrum philosophy on your work with small differences or by calling it with different names. It's all about organizing work based in the previously specified objectives or goals. Two Scrum elements you can easily incorporate into your work management are:

Defining a Product Backlog: these are the objectives and scope of the product or service to be developed. What you want to achieve, based on the budget and customer needs.

Organizing work into Sprints: each of the phases of the project where the advances are presented to the client. This proves it as it is and suggests changes. These receive a priority according to their importance, and become urgent or are assigned to a second backlog. Dividing the product into sprints will help you reach the desired product through recurring iterations.

Another important part of the Scrum Methodology are team members and their roles. The Scrum Team is divided into three parts:

Product Owner: is the person who knows the business best and decides what improvement or task has to be done in each sprint. It is the channel between managers, investors, clients and development team. Being the person who knows the market and the product best, he/she is the one who makes the final decision.

Development Team: it is recommended to be integrated between 3 and 9 members. It has to be a multifunctional team with defined internal roles required to get the job done (Frontend developers, Backend developers, QA). The interesting thing about this team is its self-management. They themselves decide the work done in each sprint (based on the priorities defined by the Product Owner), and they themselves decide how to perform each of the tasks. It is a team work, without hierarchies.

Scrum Master: being a process that comes out of the ordinary, it is normal that there is resistance from the company or from the Scrum Team members themselves. This is where the Scrum Master comes in, to ensure that everyone follows the process correctly, gives continuous coaching when there is a blockage and eliminate any impediments that arise throughout the sprint.

Depending on the size of your company and team members you can easily adapt each role and its functions. For instance, maybe in small teams Scrum Master and Product Owner tasks can be handled by a Project Manager.

It's essential that all employees are aware of the adopted methodology and its advantages. Giving a workshop explaining how it works and how your company will put it into practice is a great starting point. This may be a very important first task for the designated Scrum Master.

Also, meetings are crucial. Depending on the team size, meetings can be daily, weekly, or one per sprint. It's a matter of trying what's best for each team. However, it is highly recommended to share individual progress within the team on a daily basis. These are two of the Scrum meetings to get inspired by or try implementing:

Sprint Review: is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint.

Sprint Retrospective: is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. Often occurs after the Sprint Review and prior to the next Sprint Planning.

Moreover, to start improving your performance, any agile methodology requires of some basic tools in order to get an effective comunication between team members and get the work done. Here are some of the most popular ones:

Trello, Jira: get a better project control with a Trello or Jira board, organizing board columns based in the Kanban Methodology: organize work into Backlog, Doing and Done. This way, each card is a task to do, running or finished, helping the team know at a glance the project status and pending tasks. Kanban is widely used within the Scrum methodology, although it also works outside it independently. You may also add more columns, for other stages such as QA, In review and even one for each sprint.

Jenkins: a type of open source software, Continuous Integration oriented. This allows to approach different goals such as early feedback, avoiding merge hell, enabling merciless refactoring among a team and ensuring working software.

Git: another very standardized software to use agile methodology in programming. Besides the benefits of flexibility and distribution, there are key functions of Git that support and enhance agile development. Changes can get pushed down the deployment pipeline faster than working with monolithic releases and centralized version control systems.

Hope you found this useful! Do not wait and start getting great results by incorporating some elements of this agile methodology in your projects.

Source:

...

More about Eudaimonia: https://www.eudaimonia.com.ar

DEV Community: Euda

¡Ayuda! Necesito una APP

Comunicar en la virtualidad

Oportunidades de negocio

PWA o Progressive Web Apps

Asesorate SIN COSTO

#EudaStyle, long-term quality

We build software with processes that help your digital project take off

Cross-code control

Quality Assurance

Agile Methodologies

Multiple development environments

Automation: continuous integration, delivery and deployment

Redirect 301 con CloudFront y Lambda@EDGE

¿Qué es un Código de estado de respuesta HTTP 301?

Manos a la obra

404 error: QA Analyst not found

The demand for IT specialists

Quality Assurance

The complexity of testing

#EudaStyle, long-term quality

We build software with processes that help your digital project take off

#EudaStyle, calidad a largo plazo

Sails development with Docker and Docker Compose

Whats and whys: Docker & Docker Compose

Containerization

Docker and Docker Compose

Installing Docker

Sails containerization

Sails CLI image

Creating a new Sails project

Running and debugging

Docker compose

Database containerization

Certificación de dominio con Let’s Encrypt, NGINX y Docker Compose

Algunas definiciones

¿Qué es un Certificado SSL?

Let’s Encrypt

Certbot

Nginx

Cómo certificar

Pre-Requisitos

Pasos

Certificación de dominio con Let’s Encrypt, NGINX y Docker Compose | by Matias Quintana | Euda | Medium

Matias Quintana ・ Sep 3, 2020 ・ Medium

Development & Operations

My work as DevOps

Where to start

What is Docker?

Everything you need to know about Docker | by Euda | Euda | Medium

Euda ・ Oct 16, 2019 ・ Medium

What is Jenkins?

Good practices and recommendations

What differentiates a Junior DevOps from a Senior?

The 2023 DevOps RoadMap | Javarevisited

javinpaul ・ Apr 30, 2024 ・ Medium

Working from home during lockdown

Manage times and spaces

Do not lose communication

Knowing when and how to stop

📌📌ATENCIÓN: OFERTA LABORAL📌📌

Improve your performance with Scrum Methodology

Matias Quintana ・ Sep 3, 2020 ・
Medium

Euda ・ Oct 16, 2019 ・
Medium

javinpaul ・ Apr 30, 2024 ・
Medium