Ir al contenido principal

Getting Docker Syntax In Gedit

I have been working with docker in the last days, and encounter the syntax issue with gedit. Just pure plain text. So make a small search and found an easy way for fixing this. I found Jasper J.F. van den Bosch repository in GitHub and found the solution for this simple problem.
We need to download the docker.lang file, available here: https://github.com/ilogue/docker.lang/blob/master/docker.lang

After that, you go to the folder you save the file and do the following command.
sudo mv docker.lang /usr/share/gtksourceview-3.0/language-specs/ 
If this doesn't work you can try the following:

sudo mv docker.lang  ~/.local/share/gtksourceview-3.0/language-specs/
And that's all!

Screenshot of gedit with no docker lang


Screenshot of gedit with docker lang


Comentarios

Entradas populares de este blog

Find which devices are connected to our network

Sometimes, we want to know how many devices are connected to our network. With any Unix OS you get easily know this. For this small tutorial we´re going to use Lubuntu 16.04.

We will use nmap. Nmap (Network Mapper) is a security scanner. It is used to discover hosts and services on a computer network.

For installing it, we first do

sudo apt-get install nmap
If we just need to identify the host names

 sudo nmap -sL 192.168.0.1/24  The result of this command will be

Starting Nmap 7.01 ( https://nmap.org ) at 2016-10-02 12:39 CST
Nmap scan report for 192.168.0.0
Nmap scan report for 192.168.0.1
Nmap scan report for 192.168.0.2
Nmap scan report for 192.168.0.3
Nmap scan report for 192.168.0.4
Nmap scan report for 192.168.0.5


If we need to know the OS of the devices we have connected we do a:

sudo nmap -O 192.168.0.1/24
The address 192.188.0.1 depends of your network, you should do a ifconfig for knowing yours.
The result of this command will be something like this:

Nmap scan report for 192.168…

La ultima alegría de los sampedranos del 2017

El año 2017 esta por terminar, y para la ciudadanía de la capital industrial ha sido un año singular. La ciudad se enorgullecía de que en nuestro Aeropuerto Ramon Villeda Morales, íbamos a tener el único vuelo directo entre Europa y Honduras. Finalmente se empezaba a ver obras de infraestructura concluyendo en el tiempo establecido. Se podían observar los cruces de cebra en las intersecciones de la tercera avenida y primera calle, aparte que los conductores empezaron a respetarlos, y no digamos los semáforos peatonales que lindo es ver como la ciudadanía espera su momento para cruzar por el lugar que le corresponde.

Parecía que este 2017 iba a ser un año de alegrías para la ciudad, y que no iba a suceder  algo que lo podría devastar esas pequeñas alegrías que nos hacían olvidar todas esas políticas de gobierno provenientes de la capital, que han perjudicado al  territorio nacional y no digamos a la ciudad que produce mas del 40% del PIB del país .

Llegaban las elecciones y el actual a…

Access to AWS Postgres instance in private subnet

I have been working with AWS in the last days and encounter some issues when using RDS.  Generally when you're working in development environment you have setup your database as Publicly accessible and this isn't an issue. But when you're working in Production. So we place the Amazon RDS database into a private subnet. What we need to do for connecting to the database using PgAdmin or other tool?

We're going to use one of the most common methods for doing this. You will need to launch an Amazon EC2 instance in the public subnet and then use it as jumping box.

So after you have your EC2, you will need to run the following command.
See explantion below

After this, you will need to configure your PgAdmin.
The host name will be your localhost, the port is the same you define in the above command.
Maintenance database will be your DB name and the username you have for connecting.

Hope this helps you connect to your databases.