DEV Community: Eduardo Garcia

Supporting SQL ops - Please Don't Be a Bottleneck

Eduardo Garcia — Wed, 06 Aug 2025 11:15:58 +0000

Let's get this straight: In a prod environment you should be having DQL access to the DB's of the applications you support. Any other command belonging to DML, DDL etc are usually reserved to either DBA teams or you will need to go through your organization's formal deployment process. Do not cowboy the system, no exceptions.

From a resiliency point of view, the absolute bare minimum is to run two database instances on separate hosts. These are usually named prod and a prod-replication (or prod-replica/prod-repl). These instancess MUST live on entirely different infrastructure, be it different physical hosts or even better, different availability zones. If your primary replication is in the same rack or worse: on the same physical host (I have seen this happened (╯°□°)╯), you have not built resilient infrastructure, you created a single point of failure and a post-mortem document that will be very difficult and akward to explain after that outage that will render your db unusable.

The two-instance set-up is not only to switch to the healthy server during an outage. It also helps to solve an operational need: providing your support teams with read-only access to the data of the applications they manage. By offloading all those SELECT queries to replication, you provide your teams the visibility they need to do their jobs without consuming resources from the production DB.

Not only you will address the issue of ensuring availability and disaster recovery to your prod operation but will also address an overlooked but, necessary operational need: providing your operations team with DQL access to the data of the applications they support.

Making your operations team to file a ticket and wait for approval just to run a SELECT query is an auto sabotage that will cripple the sla to reply to business requests and slow down incident response. I can honestly just think of two reasons to do this, a dysfunctional IT culture or a lack of trust in the people running the systems.

"But what can I do if a table contains PII or sensitive data" I hear you ask. If a table contains data falling under GDPR or HIPAA regulations, the answer will never be to lock the door and throw away the key, but implementing modern security controls like data masking, column level security and/or granular roles to strike a balance between providing access to your ops teams and being compliant with security policies. Is not 2005 anymore, we have better tools, better practices. Lets keep discipline in operations and implement them.

This is an extract of a sort of practical crash course in SQL that I am working on. You can access it here: sql-crash-course

Happy coding,
Eduardo.

How to upload Markdown files to Dev.to from GitHub

Eduardo Garcia — Wed, 15 Jan 2025 11:32:44 +0000

How to upload Markdown files to Dev.to from GitHub

This is a test post to show how to upload Markdown files to Dev.to.

You can do this with:

GitHub actions
Dev.to API Token
A custom GitHub action
A Python script

I am assuming you have a general knowledge with GitHub actions and Python scripting, but you can achieve this with a superficial knowledge. To know more about it, you can check the GitHub documentation.

GitHub action to upload Markdown file

You can use GitHub actions to automate the process of uploading Markdown files to Dev.to. Using this action will make your life easier as every time you push a new commit to your repository, the markdown document will be pushed as well. There are already several actions available that can help you with this task or you can create your own action, but why reinvent the wheel?

I did some quick research and initially decided to use this Publish to dev.to GitHub action. It's simple to use and gets the job done. Or so I thought, after 2 failed repositories and a bunch of attempts I falled back to the conventional curl POST method. To be fair, is probably due to my lack of knowledge in GitHub actions, but I will try to use it again in the future.

First, fetch your DEV.TO API key. For this, log in to your DEV.TO account and go to settings/extensions, scroll all the way to the bottom and in you will see a section Named "DEV Community API Keys". Name your project and click on "Generate API Key". Copy this key and save it in your GitHub repository secrets.

To save the key as a secret. go to your repository settings, click on secrets, and add a new secret with the name DEVTO_TOKEN and paste the key you copied from DEV.TO. Ensure you have saved at repository level.

In your repository, create a new file called .github/workflows/devto_publish.yml and add the following code that you can find here.

name: Publish to Dev.to

on:
  push:
    branches:
      - main
    paths:
      - 'posts/**'

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout repository
      uses: actions/checkout@v3

    - name: Set up Python
      uses: actions/setup-python@v4
      with:
        python-version: '3.11'

    - name: Upgrade pip and Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install pyyaml requests

    - name: Verify API Key Availability
      env:
        DEVTO_API_KEY: ${{ secrets.DEVTO_API_KEY }}  # Keep existing secret mapping
      run: |
        echo "API key character count: ${#DEVTO_API_KEY}"
        echo "API key empty check: $([ -z "$DEVTO_API_KEY" ] && echo 'Empty' || echo 'Set')"

    - name: Convert md to Dev.to format
      run: |
        python publish_script.py ./posts/main.md > formatted_article.json

    - name: Publish or Update to Dev.to
      env:
        DEVTO_API_KEY: ${{ secrets.DEVTO_API_KEY }}
      run: |
        action=$(jq -r '.action' formatted_article.json)
        article=$(jq -r '.article' formatted_article.json)

        if [ "$action" = "create" ]; then
          response=$(curl -X POST "https://dev.to/api/articles" \
            -H "api-key: $DEVTO_API_KEY" \
            -H "Content-Type: application/json" \
            -d "$article" -w "\n%{http_code}")
        elif [ "$action" = "update" ]; then
          article_id=$(echo $article | jq -r '.id')
          response=$(curl -X PUT "https://dev.to/api/articles/$article_id" \
            -H "api-key: $DEVTO_API_KEY" \
            -H "Content-Type: application/json" \
            -d "$article" -w "\n%{http_code}")
        else
          echo "Invalid action: $action"
          exit 1
        fi

        status_code=$(echo "$response" | tail -n1)
        if [ "$status_code" -ne 200 ] && [ "$status_code" -ne 201 ]; then
          echo "Failed to update article. Status code: $status_code"
          exit 1
        fi

Brief explanation of GitHub action

Triggers when there's a push to the main branch that modifies files in the posts/ directory
Sets up the environment:
- Runs on ubuntu-latest
- Checks out the repository
- Configures Python 3.11
- Installs required dependencies pyyaml and requests
Performs API key validation by checking its presence and length
Executes the publishing process:
- Converts markdown files to Dev.to format using a Python script
- Generates a formatted JSON article output
Handles article publication:
- Determines whether to create new or update existing article
- Makes appropriate API calls to Dev.to - POST for new, PUT for updates)
- Includes proper headers and authentication using DEVTO_API_KEY
Includes error handling:
- Validates HTTP response codes
- Exits with failure if status code isn't 200 or 201
- Provides detailed error output for troubleshooting1

The python script

This Python script handles the conversion and publishing of markdown files to Dev.to. Here's a breakdown of its main components. The script's main purpose is to convert markdown files to Dev.to API format and verify existing articles1

extract_front_matter Function

Takes a markdown file path as input and returns:
- A dictionary containing parsed YAML front matter data
- The markdown body content without the front matter1
Handles errors for:
- Missing files
- Invalid YAML parsing1

md_to_devto Function

Accepts:
- Markdown file path
- Dev.to API key
- Returns:
- JSON string of the article
- Action string ('create' or 'update')1
Key operations:
- Extracts front matter and body
- Validates required fields (title, tags)
- Checks for existing articles
- Prepares article JSON with title, published status, content, and tags1

fetch_existing_articles Function

Takes API key as input
- Returns list of existing articles from Dev.to
- Raises HTTP errors for failed requests1
Main Execution
- Validates:
- Command line arguments
- API key presence Outputs:
- Formatted JSON result with article data and action
- Error messages to stderr on failure

Conclusion

The script and GitHub action provided in this article can help you automate the process of uploading markdown files to Dev.to. However, needs to be modified to incorporate more of the error handling in Pyton and create a more robust and maintainable solution. I hope this article helps you in your journey to automate your workflow and make your life easier.

I will create an updated version of this scripts with a new article in the future, so stay tuned for that.

Cheers and happy, happy coding!

Eduardo Mendoza

After installing Fedora 41: A Glorious Adventure Awaits!

Eduardo Garcia — Thu, 26 Dec 2024 09:47:21 +0000

After installing Fedora 41: A Glorious Adventure Awaits!

Welcome, brave linux enthusiasts, to the land of Fedora 41! You've just embarked on a journey where your terminal is your sword, and your bash commands are your spellbook. Here's how to make your new digital home not just functional but confortable as well.

Update system

First things first, let's ensure your Fedora fortress is up to date. Run these commands to banish the outdated demons:

sudo dnf upgrade -y
# sudo dnf update -y
# upgrade is now the preffered command, it has backwards compatibility

Because nothing says "I installed a new Linux" like a good old system update.

Configure DNF simultaneous mirrors

Cast a speed spell to your dnf sources by enabling max downlows parameter.

sudo vi /etc/dnf/dnf.conf

# then add and wq
add max_parallel_downloads=10

Now, your downloads will race through the internet like Usain Bolt on a caffeine rush... or me when someone mentions 'production outage'.

dnf Plugins

DNF plugins are like magical accessories for your package manager. They add extra features to the dnf package manager and provide some essential plugins. Here is how to arm yourself with them:

sudo dnf install dnf-plugins-core -y

builddep: This plugin allows you to automatically install the build dependencies for a package. This is useful if you want to compile software from source code.
changelog: This plugin lets you view the changelog for a package, showing the changes made in each version. Who doesn't love a transaction log?
config-manager: This plugin helps you manage DNF configuration options and repositories.
copr: This plugin enables you to install packages from COPR, a community-driven repository for Fedora packages.
debug: This plugin installs debugging information for packages, which can be useful for developers.
debuginfo-install: This plugin installs debuginfo packages, which contain debugging symbols for programs.
download: This plugin allows you to download RPM packages without installing them.
needs-restarting: This plugin checks for and reports on processes that need to be restarted after package updates.
versionlock: This plugin allows you to lock specific packages to a particular version, preventing them from being updated.

Install SW

Proton Fedora VPN

Feeling the need for privacy? Here’s how to cloak yourself with ProtonVPN or follow the guide: https://protonvpn.com/support/official-linux-vpn-fedora/


wget "https://repo.protonvpn.com/fedora-$(cat /etc/fedora-release | cut -d' ' -f 3)-stable/protonvpn-stable-release/protonvpn-stable-release-1.0.2-1.noarch.rpm"

sudo dnf install ./protonvpn-stable-release-1.0.2-1.noarch.rpm

sudo dnf check-update && sudo dnf upgrade

sudo dnf install --refresh proton-vpn-gnome-desktop

sudo dnf check-update && sudo dnf upgrade

sudo dnf install libappindicator-gtk3 gnome-shell-extension-appindicator gnome-extensions-app

Don't forgent to restart and enable AppIndicator and KStatusNotifierItem Support extension for that sweet, sweet VPN icon.

Install IVPN

If ProtonVPN feels too mainstream, or you're just looking for a faster alternative, IVPN might be your speed demon.

Its pretty much anonymous, pay with crypto if you're feeling cyberpunk.

# [Fedora 41+] Add the IVPN repository
sudo dnf config-manager addrepo --from-repofile=https://repo.ivpn.net/stable/fedora/generic/ivpn.repo

# To install IVPN software (CLI and UI)
sudo dnf install ivpn-ui

# To install only IVPN CLI
sudo dnf install ivpn

This is for Fedora 41, for below versions go here: https://www.ivpn.net/en/apps-linux/#fedora

Install all of this cool stuff

Recommended by yours truly (づ ◕‿◕ )づ, assuming you've already embraced the magic of rpmfusion-nonfree:

sudo dnf5 install fastfetch mpv unrar p7zip p7zip-plugins htop android-tools vlc discord dejavu-sans-mono-fonts fira-code-fonts kdenlive easyeffects

Some Devtools for Your Spellbook

To expand your arcane library:

sudo dnf5 install gcc make python3-pip python3-tools cargo nodejs vim java-17-openjdk gh development-tools

To enhance your python spell tree, check this guide. It's crucial if you're delving deep into Python on Fedora.
gh is very important when you conjure local repos and you need to reflect them in GitHub. Check this grimoire to learn this magic.

With these enchantments, your Fedora journey be filled with wonder and productivity!

VSCode

Because who doesn't love an editor that thinks it's an IDE? Add repo from here: https://code.visualstudio.com/docs/setup/linux#_rhel-fedora-and-centos-based-distributions

then:

dnf check-update
sudo dnf install code

Vim plugins

Make Vim as fancy as your socks. Ensure you always have the latest repo:

curl -fLo ~/.vim/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim

This command downloads the plug.vim file and installs it in ~/.vim/autoload. If the directory doesn’t exist, it will be created. To verify installation, open a new Vim session and type :PlugVersion to verify that Vim-Plug is installed correctly.

Here’s a list of plugins that will make you feel like a coding wizard:

" Plugins
call plug#begin('~/.vim/plugged')
Plug 'junegunn/vim-plug'
" Python
Plug 'davidhalter/jedi-vim'
Plug 'preservim/nerdtree'
" GH Copilot
Plug 'github/copilot.vim'
" markdown
Plug 'plasticboy/vim-markdown'
Plug 'shime/vim-livedown'
" Fuzzy finder
Plug 'junegunn/fzf', { 'do': { -> fzf#install() } }
Plug 'junegunn/fzf.vim'
call plug#end()

Vim GitHub copilot setup:

Your perfect AI buddy

:Copilot setup This command will prompt you to authenticate with GitHub. You'll get a code to enter on a GitHub login page that opens in your browser. Follow the instructions to authorize Copilot.
To accept a suggestion, press Tab.
For more information on usage, you can check the plugin's documentation with :help copilot.
If you encounter issues, check the status with :Copilot status

" Toggle GitHub Copilot on and off
nnoremap <leader>cc :Copilot disable<CR>
nnoremap <leader>ce :Copilot enable<CR>

function! CopilotStatus()abort
    return exists('*copilot#Enabled') && copilot#Enabled() ? 'enabled' : 'disabled'
endfunction

nnoremap: Non-recursive mapping in normal mode.
<leader>cp: This is the shortcut; is typically , by default, but you can change it in your config. So, this would be ,cc if you haven't changed your leader key.
:Copilot diable/enable: This is the command to enable/disable Copilot.
<CR>: Simulates pressing Enter to execute the command.

Timeshift

Similar to system restore in Windows. Consider it your Fedora's time machine.

sudo dnf install timeshift

sudo timeshift --create

sudo timeshift --restore

timeshift --list

YTMusic player (⌐■_■)

For those who like their music with a side of Linux. Go to https://ytmdesktop.app/#download and download your rpm.

# go to Downloads and rpm, substitute with your own version
sudo rpm -ivh youtube-music-desktop-app-2.0.6-1.x86_64.rpm

to update:

sudo dnf5 update <package_name>
# rmp may not solve al dependencies while dnf does

Docker -- edit: Just skip this and use Podman

Very important: At the moment of writing, Fedora 41 includes Podman as the default container runtime. If you want to use Docker, you need to install it manually, which is only advisable if you really need Docker. Docker will just override Podman. So I would suggest you to actually skip this step and use Podman. It will be cleaner if you need to use containers. I have to use it as I am completing a course that requires Docker.

First update system, we will be installing community edition.

# sys update
sudo dnf update -y
# add repo from docker address, check this, dont blindly copy pls
sudo dnf config-manager --add-repo=https://download.docker.com/linux/fedora/docker-ce.repo
#install
sudo dnf install docker-ce docker-ce-cli containerd.io docker-compose-plugin -y

You will be asked if you wanto enable docker since boot which I don't want as this is for personal and not a corporate environment where you probably want it that way.

# this will start docker
sudo systemctl start docker
# thiw will enable boot run
sudo systemctl enable docker

Terminal Transparency

Credits to this Reddit post.

Ptyxis is the default terminal for Gnome, it was previously known as Prompt. To change transparency just run the below:

gsettings set 'org.gnome.Ptyxis.Profile:/org/gnome/Ptyxis/Profiles/'$PTYXIS_PROFILE'/' 'opacity' '0.8'

.8 is currently working fine for me, just try and adjust to your taste.

Aliases

Fedora points your bashrc file to /etc/bashrc to have a cleaner config. To have your own, create a bashrc.d directory and then put whatever you want. It would be more useful that you know these before aliasing

These are some linux aliases I use on my day to day.
Upme and py_gitignore command are fast casting a full update and the standard .gitignore file aimed to python development
fastfetch command at the end is to run fastfetch at terminal startup.

mdkir ~/.bashrc.d
vi ~/.bashrc.d/aliases.sh

# then save and wq the below commands
alias ll='ls -lrth --color=auto'
alias la='ls -lrtha --color=auto'
alias df='df -hT'
alias d1='cd ..'
alias d2='cd ../..'
alias d3='cd ../../..'
alias d4='cd ../../../..'
alias upme='sudo dnf5 upgrade -y'
alias py_gitignore='curl https://raw.githubusercontent.com/github/gitignore/main/Python.gitignore > ./.gitignore'

fastfetch

To not use any alias and run the standard command:

\df

#or

command df

upgrade is the preferred term: In DNF5, upgrade is the technically correct and recommended command for updating packages.
update is an alias: update still works because it's maintained as an alias for upgrade for backward compatibility and user familiarity

In older dnf and yum versions, there was a distinction between update and upgrade, where upgrade was usually reserved for version upgrades, like from Fedora 36, to 37.

Custom DNS

Feel like you are on a secret scenario quest with this setup.

In terminal, run resolvectl, you will probably be running under your ISP's DNS server and this command will show it. The most common DNS servers are Google and Cloudfare.

Cloudflare:
- Primary DNS: 1.1.1.1
- Secondary DNS: 1.0.0.1
Google Public DNS:
- Primary DNS: 8.8.8.8
- Secondary DNS: 8.8.4.4

$ nmcli connection show

NAME                UUID                                  TYPE      DEVICE
Wired connection 1  f87e2a6c-b089-31d3-ba62-83e08188db2a  ethernet  enp9s0
virbr0              9ad8ea46-a589-43f7-a904-95098b18404f  bridge    virbr0

Explanation of the columns:

NAME: The name assigned to the network connection. This is usually how you identify the connection in NetworkManager.
UUID: A universally unique identifier for the connection.
TYPE: The type of network connection (e.g., ethernet, Wi-Fi, bridge, VPN).
DEVICE: The network interface associated with the connection (e.g., enp9s0 for a wired connection, wlan0 for Wi-Fi).

# Point DNS and Connection to your preffered service
$ nmcli con mod "Wired connection 1" ipv4.dns "1.1.1.1 1.0.0.1"

# restart network connection to apply changes
$ nmcli con down "Wired connection 1"
$ nmcli con up "Wired connection 1"

Wallpapers

Dress up your desktop with some fresh wallpaper from here: https://github.com/ropapermaker/Wallpapers/blob/main/README.md

Because even Linux needs a good aesthetic.

And there you have it! Your Fedora 41 setup should now be more than just functional; this is a statement. Now, go forth and conquer your Linux adventures with style and speed.