DEV Community: Sebastian

Docusaurus doesn't recognize brackets {} on the markdown files

Sebastian — Mon, 01 Apr 2024 23:14:14 +0000

If for any reason this happened to you, with this kind of configuration,

package.json

{
  "name": "my-websiteopenapi-3",
  "version": "0.0.0",
  "private": true,
  "dependencies": {
    "@docusaurus/core": "^3.0.0",
    "@mdx-js/react": "^3.0.0",
    "clsx": "^1.2.1",
    "docusaurus-preset-openapi": "0.7.3",
    "prism-react-renderer": "^2.1.0",
    "react": "^18.0.0",
    "react-dom": "^18.0.0",
    "url": "^0.11.0"
  },
  "scripts": {
    "docusaurus": "docusaurus",
    "start": "docusaurus start",
    "build": "docusaurus build",
    "swizzle": "docusaurus swizzle",
    "deploy": "docusaurus deploy",
    "clear": "docusaurus clear",
    "serve": "docusaurus serve",
    "write-translations": "docusaurus write-translations",
    "write-heading-ids": "docusaurus write-heading-ids"
  },
  "browserslist": {
    "production": [
      ">0.5%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

and your docusaurus.config.js looks like this:

// @ts-check
// `@type` JSDoc annotations allow editor autocompletion and type checking
// (when paired with `@ts-check`).
// There are various equivalent ways to declare your Docusaurus config.
// See: https://docusaurus.io/docs/api/docusaurus-config

import { themes as prismThemes } from "prism-react-renderer";

/** @type {import('@docusaurus/types').Config} */
const config = {
  title: "My Site",
  tagline: "Dinosaurs are cool",
  url: "https://your-docusaurus-test-site.com",
  baseUrl: "/",
  onBrokenLinks: "throw",
  onBrokenMarkdownLinks: "warn",
  favicon: "img/favicon.ico",
  organizationName: "facebook", // Usually your GitHub org/user name.
  projectName: "docusaurus", // Usually your repo name.
  presets: [
    [
      "docusaurus-preset-openapi",
      /** @type {import('docusaurus-preset-openapi').Options} */
      ({
        docs: {
          sidebarPath: require.resolve("./sidebars.js"),
          // Please change this to your repo.
          editUrl: "https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/",
        },
        blog: {
          showReadingTime: true,
          // Please change this to your repo.
          editUrl: "https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/",
        },
        theme: {
          customCss: require.resolve("./src/css/custom.css"),
        },
      }),
    ],
  ],

  themeConfig:
    /** @type {import('docusaurus-preset-openapi').ThemeConfig} */
    ({
      navbar: {
        title: "My Site",
        logo: {
          alt: "My Site Logo",
          src: "img/logo.svg",
        },
        items: [
          {
            type: "doc",
            docId: "intro",
            position: "left",
            label: "Tutorial",
          },
          { to: "/api", label: "API", position: "left" },
          { to: "/blog", label: "Blog", position: "left" },
          {
            href: "https://github.com/facebook/docusaurus",
            label: "GitHub",
            position: "right",
          },
        ],
      },
      footer: {
        style: "dark",
        links: [
          {
            title: "Docs",
            items: [
              {
                label: "Tutorial",
                to: "/docs/intro",
              },
            ],
          },
          {
            title: "Community",
            items: [
              {
                label: "Stack Overflow",
                href: "https://stackoverflow.com/questions/tagged/docusaurus",
              },
              {
                label: "Discord",
                href: "https://discordapp.com/invite/docusaurus",
              },
              {
                label: "Twitter",
                href: "https://twitter.com/docusaurus",
              },
            ],
          },
          {
            title: "More",
            items: [
              {
                label: "Blog",
                to: "/blog",
              },
              {
                label: "GitHub",
                href: "https://github.com/facebook/docusaurus",
              },
            ],
          },
        ],
        copyright: `Copyright © ${new Date().getFullYear()} My Project, Inc. Built with Docusaurus.`,
      },
      prism: {
        theme: prismThemes.github,
        darkTheme: prismThemes.dracula,
      },
    }),
};

export default config;

and you have a markdown file in the browser that looks like the next image:

this will be the solution to your problem:

Amazon Workspace problems with SSH Key

Sebastian — Mon, 04 Mar 2024 22:54:17 +0000

Sometimes the Amazon Workspace restarts, and if you already created the SSH Key, and after you restart the workspace you can't push any change to Gitlab, you can do it again with this command.

ssh-add KeyToAddSSH

Then you can push your changes without any problem.

Happy Coding!!!

Download and Install pip on Windows

Sebastian — Mon, 19 Feb 2024 22:41:32 +0000

The PIP can be downloaded and installed using the command line by going through the following steps:

Using cURL in Python

Curl is a UNIX command that is used to send the PUT, GET, and POST requests to a URL. This tool is utilized for downloading files, testing REST APIs, etc.

Step 1: Open the cmd terminal

Step 2: In Python, a curl is a tool for transferring data requests to and from a server. Use the following command to request:

curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py

python get-pip.py

Happy Coding!

K8S - exercise 1: create, fix, get, and delete PODS

Sebastian — Sun, 04 Feb 2024 23:49:05 +0000

This exercise is based on the course LinuxFoundationX LFS158x
Introduction to Kubernetes.

Create a pod in a declarative way

create a file called pod.yaml

touch pod.yaml
vim pod.yaml

past this code in pod.yaml

apiVersion: v1
kind: Pod
metadata:
  name: nginx
spec:
  containers:
    - name: nginx
      image: nginx:1.14.2
      ports:
        - containerPort: 80

Run the command:

kubectl create -f pod.yaml

Create a pod in a imperative way

kubectl run firstrun --image=nginx

Get pods to see the new pod:

kubectl get pods
kubectl get pods -o wide

Create a pod in a mix way (declarative and imperative)

kubectl run firstrun --image=ngixx --port=88 --dry-run -o yaml > secondrun.yaml

If you notice, I introduced some errors in the YAML file so that I can fix them.

Modify because it is not possible to have two pods with the same name and label:

name, label, container -> name

kubectl describe secondrun

Run this command, to replace the previous pod:

kubectl replace --force -f secondrun.yaml

Now let's delete the pods:

kubectl delete -f pod.yaml

kubectl delete pods firstrun secondrun

Part 2 - Create an instance of EC2 and connect with SSH

Sebastian — Sun, 21 Jan 2024 16:02:47 +0000

Hi!

Create an instance of EC2 (Amazon Elastic Compute Cloud) allows execute instances of virtual machines, on the AWS infrastructure.

Some features of EC2 are Scalability, personalized configuration, Security, and pay-by-use.

Create an instance of EC2 (Amazon Elastic Compute Cloud) allows execute instances of virtual machines, on the AWS infrastructure.

Some features of EC2 are Scalability, personalized configuration, Security, and pay-by-use.

Create an EC2 and connect with SSH
1. Go to the EC2 service.
2. On the left menu, click on Instances.
3. Add a new name to the instance
4. Let Amazon Linux, everything that has the free tier label.
5. Create a key pair.
6. Add a name
7. and let the RSA and .pem options be selected.
8. Click on the Create key pair button.
9. Save in a secure place on your laptop or PC.

Create a security group:
1. Allow SSH traffic from
2. Click Lunch instance.
3. Check the instances.
4. Click on the connect button.
5. Select the SSH client tab
6. Follow the steps. Note: if you are in Windows, use the git bash terminal if the connection with another terminal shows an unprotected private key file! message.

After connect:

Check the instances:
1. If you want to check the instances from your CLI, type

aws ec2 describe-instances

Delete the instance:
1. Go to your instance
2. Choose Instance State
3. Select Terminate Instance

See you next time!

Part 1 - Create an account in AWS and start to play with some services

Sebastian — Mon, 08 Jan 2024 22:17:12 +0000

Hello!

First, this is my diary about my experience, learning the path to the cloud and the focus on Amazon Web Services (AWS).

Don't forget that the account is a free tier, which means you have 12 months of almost 100 services to try.

I will update every time I continue this journey.

Happy cloud!

1.Create an AWS account.

Go to the https://aws.com/free
Follow each of the steps
Remember your credit card and your cell phone to validate your identity.
After you receive the validation, go to the AWS Management Console.
Because this is your first time logging, select Root user, and type your email and password.

2.Set up MFA for the Root user

Extra larger protection for my account.
Go to the service IAM (Identity and Access Management) to manage resource access.
Click on Add MFA
Add a name on the device name
Select an MFA device, in my case I use the Authenticator app.
Click on the Next button.
Note: I fill both MFA codes with two different values.
Add MFA.
After all of this, refresh if you do not see any change in the security recommendations:

3.Create a new user admin detached from the root user.

Go to users on the left menu.
Click Add User.
Next.
Set permissions: this is because I’m the same root and admin user 😉
Then next, create a user, and next.
After this step, AWS will show a Retrieve password, that has 3 things → 1. Console sign-in URL (Save in some bookmark) 2. User name 3. Console password
The first is the URL with the ID associated with the user. We will use this to access the AWS Console.

4.Enable billing alarm: This is important to monitor your cost, even if there is a free tier.

Go to the service Billing and cost management
Next, in the left menu, Preference → Billing preferences
On the box Alert Preferences, click on the Edit button.
Select Receive AWS Free Tier alerts, it is not necessary to type the email.
Select Receive CloudWatch alerts.
Click on the Update button.
This will show this message.

5.Create a billing alarm using the CloudWatch console:

Go to the service CloudWatch
Choose alarms
Create Alarm
Note: Select the us-east-1 region if you do not see the Billing/Total Estimated Charge
Select metric → choose Billing → and choose Total Estimated Charge → select USD

Then Select the metric
Let's almost like this show, and type the maximum amount of money, in this case, 5 USD
If the amount of money exceeds 5 USD, then an email will be sent to you
Click Next.
Create a Notification and a new topic:
Click on Create topic.
Click on Next.
Add a Name to the alarm Name → Click on Next.
Check everything is fine and click on Create alarm.
Check your email and confirm the subscription on the topic.
Refresh the dashboard alarm.

6.Add MFA for the admin user

log-in with the link provided when it was created.
Go to the IAM service
Select Assign MFA
It is the same process that we did for the root user.

7.Set up the AWS CLI

Go to https://aws.amazon.com/cli/?nc1=h_ls
Download the CLI for Windows in my case.
Install the console.

8.Link the AWS CLI with your account AWS

Go to the IAM service.
Select Users on the left menu.
In the Right menu select My Security credentials
Go to the section Access keys
Click on Create access keys
Select Command Line Interface (CLI)
Select: I understand the above recommendation and want to proceed to create an access key checkbox.
Click Next → Click the Create access key button.
Validate AWS CLI is installed
you can use the aws —version command too.
Now configure the connection with the previous access keys.

See you next time!

10 lessons that I learned in 2023, apply for life and work

Sebastian — Tue, 19 Dec 2023 21:53:07 +0000

Hello!

This year, was a very challenging year for me.

I wrote these lessons in one sentence to reflect on what you can improve in your daily life.

This lesson applies as well to your job.

Have a bright 2024!

1. Love with passion!
2. Do not complicate things!
3. Clean mind to make decisions.
4. Rely on data to make your decisions.
5. Break the requirements into one sentence.
6. Learn from those who want to teach you something.
7. Simple systems, process the most complex problems.
8. You will find the solution after doing a lot of research.
9. Do not jump to conclusions before having enough information.
10. Find the details about something that I don’t know, details are important.

Uninstall docker that was install with Ubuntu software

Sebastian — Wed, 29 Nov 2023 01:21:38 +0000

If you install docker using the Ubuntu Software on the 22.04 version, when you try to uninstall docker, sometimes is not easy way to do it.

After a will I found how to do it.

This will display a list of ongoing operations with their respective IDs:
snap changes
Find the ID of the operation you want to stop.
Stop the operation using the snap abort command followed by the operation ID:
sudo snap abort 19
Stop the snapd service to ensure the changes are applied correctly. You can do it with the following commands:
sudo systemctl stop snapd
Uninstall Docker more forcefully using the following command:
sudo snap remove --purge docker
Start the snapd server:
sudo systemctl start snapd

Happy coding 😎!!!