docker build --tag NAME-OF-THE-IMAGE:latest .
Para crearnos una imagen. A partir de esa imagen crearemos nuestro contenedor as铆:
I have a pair of excels with some interesting code I want to keep track in git. Keeping the whole excel is the easiest way to do, but I wondered how store a copy of the source files in a separate folder in order to maintain an adequate control over the source files itself.
Below is an vbs script I have to export the code of all the excel files of a directory into another directory. You have to do two things:
Here is an example of a server program and a client program that communicate each other over the network.
The server, once the client has received a connection from the client, attends the request by spawning a dedicated thread.
It's a very simple scheme that can help to develop a more complex python use cases that communicate over the network.
In the template driven approach you define the form behaviour and configuration in the template: validators, and so on.
You can find a more detailed tutorial at: https://angular.dev/guide/forms/template-driven-forms#
We will start with this simple example made in ionic (but you can do in html exactly the same):
Sometimes it's useful to do it by yourself: examining the apache logs for searching certain patterns. In that ocassions, the most cumbersome thing is to start just parsing the log file. So this script comes in handy as an start thing to suit your needs and perform just the analysis you need.
So, given this log configuration:
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
Al repartir el c贸digo en varios ficheros fuente, conseguimos estructurar nuestra aplicaci贸n en "temas": socios por un lado, cursos por otro, por ejemplo. Eso permite que la colaboraci贸n entre varias personas sea m谩s f谩cil. Pero no s贸lo eso, facilita la mantenibilidad de la aplicaci贸n.
Y adem谩s as铆 es como trabajan los profesionales, por todos estos motivos.
<form (ngSubmit)="onSubmit( f )" #f="ngForm">
In the code we can access this form as:
/** | |
* Given a Date object, returns a string representing | |
* a "useful" translation of that date. | |
* | |
* A useful representation is "two days ago" instead of | |
* "18/08/2022" or "In two hours" to represent that the | |
* event represented by this date will begin on two hours. | |
* | |
* valores que vamos a retornar: |