DEV Community: Alexandre Calaça

How to undo a specific pushed commit

Alexandre Calaça — Thu, 13 Feb 2025 17:00:20 +0000

Navigate to Your Repository:

Open your terminal

Check the Status:

Run the following command to ensure you have a clean working tree:

git status

Find the Commit Hash:

Each commit has a unique hash (e.g., 2c8451a). You need to find the hash of the commit you want to undo.

You can do this in two ways:

View the commit history on GitHub, Bitbucket, or another remote repository hosting service;
View the commit history in the terminal

Let's use the terminal.

git log --oneline

Output

Revert the Commit:

Once you have the commit hash, run the following command (replacing 2c8451a with the actual hash of your commit):

git revert 2c8451a --no-edit

The --no-edit option prevents Git from asking you to enter a commit message.

OUtput

By following these steps, you will create a new commit that effectively undoes the specified commit while keeping your Git history intact.

Push the Reverted Changes

if working with a remote repository):

git push origin feature/branch-133

This will push the reverted commit to the remote repository, ensuring that others see the changes.

Double check

In the terminal:

git log --oneline

Output

Done

Final message

MBA em Desenvolvimento de Software Avançado com foco em Ruby on Rails

Alexandre Calaça — Sat, 21 Dec 2024 20:50:06 +0000

Caríssimos,

Com o final do ano se aproximando, é um ótimo momento para refletirmos sobre tudo o que conquistamos e sonharmos com o que está por vir.

Se você está pensando em dar um passo a mais na sua carreira em tecnologia, há uma equipe dedicada de profissionais que está comprometida em oferecer o melhor para nossos estudantes e para a comunidade Rails.

É o O MBA em Desenvolvimento de Software Avançado com foco em Ruby on Rails, MBA on Rails, que foi cuidadosamente elaborado para atender às necessidades do mercado e preparar você para os desafios do mundo da tecnologia.

Você será exposto a tópicos altamente relevantes, como segurança, otimização e performance, escalabilidade, AWS, DevOps, design patterns e arquitetura de software.

Além disso, você terá a oportunidade de se conectar com uma rede de profissionais da indústria e participar de projetos práticos que fortalecerão suas habilidades, portfolio e confiança.

A partir de hoje, 21 de Dezembro de 2024, faltam apenas 25 dias para o início das inscrições do programa mais completo de Pós-Graduação Lato Sensu da América Latina, focado no ecossistema Ruby on Rails!

Não perca a chance de transformar sua carreira! Seja o primeiro a saber sobre a abertura das inscrições e o lançamento oficial em 15 de janeiro de 2025.
Link: http://mbaonrails.com.br/signup

Vaga Desenvolvedor Backend - Ruby on Rails - AGROS

Alexandre Calaça — Thu, 05 Dec 2024 17:02:54 +0000

Post original da vaga Desenvolvedor Backend - Ruby on Rails.

Descrição da Vaga

O que você vai fazer:

Desenvolver e manter sistemas utilizando Ruby on Rails.
Criar e integrar APIs REST de alto desempenho.
Trabalhar com bancos NOSQL, otimizando consultas e garantindo eficiência.

Post original da vaga Desenvolvedor Backend - Ruby on Rails.

Requisitos Desejáveis

Conhecimentos em javascript, typescript e NodeJS

Post original da vaga Desenvolvedor Backend - Ruby on Rails.

Regime de Contratação

CLT

Post original da vaga Desenvolvedor Backend - Ruby on Rails.

PCD

INDIFERENTE

Benefícios

Auxilio Educação;
Plano de Saúde Unimed;
Seguro de vida;
Vale Alimentação;
Ambiente colaborativo e de aprendizado contínuo;
Oportunidade de crescimento profissional;
Projetos inovadores e desafiadores.

Post original da vaga Desenvolvedor Backend - Ruby on Rails.

Vaga Desenvolvedor Jr - Ruby on Rails - Híbrido

Alexandre Calaça — Thu, 05 Dec 2024 16:53:09 +0000

Post de divulgação para a vaga Desenvolvedor Jr - Ruby on Rails,

Descrição da vaga

Somos a Pitzi, a proteção para celulares mais completa do mercado!

São mais de 12 anos de experiência e 2.5 milhões de aparelhos protegidos, resultado de um conceito de negócio inovador! Recentemente, a Pitzi e a Leapfone se conectaram para oferecer um novo jeito de ter um smartphone com mensalidades acessíveis e proteção completa.

Pessoas, transparência e tecnologia. Esse é o nosso combustível.

Post original da vaga aqui.

Por que a Pitzi?

Somos mais de 160 Pitziers, formando um time de alto nível, com propósito de autodesenvolvimento e voltado à estratégia de Cliente no Centro;
Trabalhamos juntos na construção de um ambiente tecnológico, dinâmico e diverso.
E, claro, somos uma empresa GPTW - Great Place to Work, certificação que identifica as melhores empresas para se trabalhar no Brasil e no mundo.
Os nossos valores guiam todas as nossas decisões. Eles estão presentes nas estratégias, projetos e no dia a dia dos Pitziers: Focamos no cliente; Sonhamos grande; Sem risco, sem graça; Amamos pareto; Somos essencialistas; Mandamos a real; Colocamos a mão na massa; Assumimos a responsa; Um por todos e todos por um; Valorizamos impacto.
Queremos pluralidade e entendemos os benefícios da diversidade. Por isso, aqui na Pitzi, todos podem ser exatamente quem são, sem qualquer distinção, a todo o momento. #DiversidadePitzi #VemPraPitzi.

Post original da vaga aqui.

Contratação CLT + Benefícios:

🍎 Flash (cartão flexível) com a recarga média de R$ 700/mês;
💰 Antecipação de Salário
😎 Uma folga no mês de aniversário;
🍕 Eventos de descompressão na sexta-feira;
🚑 Plano de Saúde Sul América;
🦷 Plano Odontológico Sul América;
💙 Seguro de Vida Prudential;
🏋🏽‍♂️ Gympass;
🏃 TotalPass;
👶🏼 Auxílio Creche;
👩🏻‍🍼 Licença maternidade estendida 180 dias;
👨🏻‍🍼 Licença paternidade estendida 30 dias;
👨‍👨‍👧 Licença parental estendida 120 dias;
🏊🏻‍♀️ Sesc SP;
💆💆‍♂️Quick Massage
📲 Proteção total Pitzi;
👩🏻‍🚀Facilitação na adesão Leapfone;
🛍️ Facilitação na adesão de celular e produtos Pitzi;
📚 Pitzi Academy – cursos focados no desenvolvimento de soft skills e hard skills;
📝Consultoria Financeira;
💸 Crédito Consignado Creditas;
💰 Bônus anual

Post original da vaga aqui.

Responsabilidades e atribuições

• Procuramos sempre escrever código limpo (fácil de entender, modificar, estender e testar)
• Procuramos cuidar do código como um jardim, sempre tentando deixar melhor do que encontramos
• Fazemos Code review por Pull Requests (PR)
• Usamos boas práticas de engenharia + metodologias ágeis
• Usamos o conceito de MVP em features. Colocamos no ar o mínimo para ser usado e validado
• Estamos sempre abertos a receber críticas construtivas sobre o código
• Buscamos a melhoria contínua em todos os processos
• Ser ágil está em nosso DNA.

Post original da vaga aqui.

Requisitos e qualificações

Trabalhamos aqui com:
• Ruby / Ruby on Rails / Ruby on Jets
• JavaScript
• Testes Automatizados
• Sistemas de Banco de Dados Relacional
• Infraestrutura Cloud-Based (AWS)

Experiência profissional nas tecnologias acima será considerado um diferencial, porém também valorizamos o conhecimento adquirido através de estudos. Não deixe de se candidatar se ainda não tiver trabalhado com alguma delas, adoramos ensinar e formar novos profissionais.

Etapas do processo

A Pitzi nasceu em 2012 com a missão de revolucionar o mercado de proteção para celular no Brasil.

Ao lado de varejistas parceiros, oferecemos a proteção de celular mais completa do mercado, com transparência e velocidade. Utilizamos tecnologia de ponta e uma abordagem inovadora para simplificar o processo de contratação e gerenciamento de proteção para smartphones, proporcionando uma experiência ímpar e totalmente digital aos clientes.

São mais de 2 milhões de aparelhos protegidos, 2 mil pontos de vendas em todo o país e 150 Pitziers apaixonados por inovação.

Pessoas, transparência e tecnologia. Esse é o nosso combustível.

How to Switch Your Rails Application Database from PostgreSQL to SQLite

Alexandre Calaça — Thu, 28 Nov 2024 18:43:25 +0000

When working on a Rails project, there might be scenarios where you want to switch your database from PostgreSQL to SQLite.

SQLite is lightweight, requires no server setup, and is a great choice for development or small-scale projects. This guide walks you through the process step-by-step.

Introduction

Changing your database in a Rails project can seem daunting, but Rails’ flexibility makes it a straightforward task. By following these steps, you'll seamlessly transition from PostgreSQL to SQLite.

Update the `Gemfile`

First, replace the PostgreSQL gem (pg) with the SQLite gem (sqlite3) in your Gemfile. Here’s how:

# Remove or comment out:
# gem 'pg'

# Add:
gem 'sqlite3', '~> 1.4'

Once updated, run the following command to install the new dependencies:

bundle install

Output

Update the database configuration

Next, update your config/database.yml file to configure SQLite as your database adapter. Here's an example configuration:

default: &default
  adapter: sqlite3
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  timeout: 5000

development:
  <<: *default
  database: db/development.sqlite3

test:
  <<: *default
  database: db/test.sqlite3

production:
  <<: *default
  database: db/production.sqlite3

This configuration defines SQLite as the adapter for all environments (development, test, and production).

Update dependencies

Ensure that your application code doesn’t use PostgreSQL-specific features (like uuid, JSONB fields, or specific SQL queries). Refactor where necessary.

SQLite has different capabilities compared to PostgreSQL. You’ll need to ensure your application doesn’t rely on PostgreSQL-specific features such as:

UUIDs: Replace UUID columns with standard IDs or compatible alternatives.
JSONB fields: Use regular text columns or serialize data into a string format.
Custom PostgreSQL Queries: Rewrite queries to be compatible with SQLite.

Carefully review your application code and migrations for any PostgreSQL-specific features and refactor as needed.

Run dependencies

After updating the Gemfile, ensure all the required gems are installed by running:

bundle install

Output

Re-create the structure

rails db:create
rails db:migrate

Output

Test your application

With everything set up, start your Rails server:

rails server

Test your application thoroughly to ensure everything works as expected. Be mindful of any features or queries that may behave differently in SQLite compared to PostgreSQL.

Conclusion

Switching your Rails project from PostgreSQL to SQLite can simplify your setup for development or small-scale applications.

SQLite’s lightweight and serverless design makes it ideal for quick iterations and testing. While PostgreSQL excels in production environments, SQLite shines when simplicity and portability are key.

Done

Let's network

Github
LinkedIn
Dev.to

How to clean up repetitive keys in .html.erb templates?

Alexandre Calaça — Mon, 18 Nov 2024 20:40:55 +0000

Introduction

Handling translations in a Rails app is an essential part of creating scalable and maintainable software, especially when supporting multiple languages.

However, as your templates become more complex, repeatedly writing long translation keys can quickly clutter your code. It’s frustrating, harder to read, and of course, prone to mistakes.

Wouldn't it be great if there were a way to simplify this while keeping your templates clean and maintainable? Good news—there is!

Situation

I found myself in exactly this situation. While working on a .html.erb file, I noticed that a single long locale translation prefix was repeated over and over.

The result? A cluttered, hard-to-read template that felt unnecessarily verbose. I wanted to make it cleaner and more readable.

Solution

Anyway, let's get down to business.

Sample file

Let’s start with a typical .html.erb file where a long translation key prefix is repeated multiple times.

Here’s a snippet that might look familiar if you’ve worked on Rails apps:

<%# app/views/mailers/sample_mailer.html.erb %>
<table bgcolor="#FFF" align="center" width="600" class="email-body" cellspacing="0" cellpadding="0">
  <tbody>
    <tr>
      <td align="left" bgcolor="#FFF">
        <h2>
          <%= t('mailers.sample_mailer.welcome_email.title') %>
        </h2>
      </td>
    </tr>
    <tr>
      <td align="left" bgcolor="#FFF">
        <p>
          <%= t('mailers.sample_mailer.welcome_email.subtitle', user_name: @user.name) %>
        </p>
      </td>
    </tr>
    <tr>
      <td align="left" bgcolor="#FFF">
        <p>
          <%= t('mailers.sample_mailer.welcome_email.body', plan_name: @user.plan_name) %>
        </p>
      </td>
    </tr>
    <tr>
      <td align="left" bgcolor="#FFF">
        <small>
          <%= t('mailers.sample_mailer.welcome_email.footer') %>
        </small>
      </td>
    </tr>
  </tbody>
</table>

In this simple example:

The translation key prefix: mailers.sample_mailer.welcome_email is repeated in every call to t.
Code Clutter: The repetitive prefix makes the template unnecessarily verbose.
Error-Prone: If the prefix changes, you’d have to update it everywhere, increasing the risk of mistakes.

This approach works, but as the number of translations increases, it quickly becomes a maintenance nightmare.

The `prefix` approach

In order to accomplish this, we're going to use the following as a local variable:

<% prefix = 'mailers.sample_mailer.welcome_email' %>

We assigned the common part of the translation key (mailers.sample_mailer.welcome_email) to a variable called prefix.

By defining the common translation key prefix in a variable or directly in the t helper, you can dramatically clean up your .html.erb templates.

Make it happen

Here’s the same .html.erb file after applying the prefix solution:

<% prefix = 'mailers.sample_mailer.welcome_email' %>
<table bgcolor="#FFF" align="center" width="600" class="email-body" cellspacing="0" cellpadding="0">
  <tbody>
    <tr>
      <td align="left" bgcolor="#FFF">
        <h2>
          <%= t("#{prefix}.title") %>
        </h2>
      </td>
    </tr>
    <tr>
      <td align="left" bgcolor="#FFF">
        <p>
          <%= t("#{prefix}.subtitle", user_name: @user.name) %>
        </p>
      </td>
    </tr>
    <tr>
      <td align="left" bgcolor="#FFF">
        <p>
          <%= t("#{prefix}.body", plan_name: @user.plan_name) %>
        </p>
      </td>
    </tr>
    <tr>
      <td align="left" bgcolor="#FFF">
        <small>
          <%= t("#{prefix}.footer") %>
        </small>
      </td>
    </tr>
  </tbody>
</table>

Why the `prefix approach

Cleaner Templates: Your .html.erb files become significantly less verbose.
Easier Maintenance: Updating a prefix is quick and straightforward.

Done

Let's network

Github
LinkedIn
Dev.to

Ruby: One of the top 5 highest-paying technologies, according to Stack overflow

Alexandre Calaça — Sat, 16 Nov 2024 04:51:13 +0000

Introduction

In the world of software development, Ruby has a unique charm that’s kept it relevant and in demand for years. Known for its focus on simplicity and developer happiness, Ruby powers some of the world’s most popular websites and applications, making it a language that doesn’t just get the job done but makes coding genuinely enjoyable.

Year after year, Ruby continues to rank among the highest-paying technologies globally, and it’s not hard to see why. Beyond its elegant syntax and the powerful Ruby on Rails framework, Ruby appeals to a wide range of businesses looking for efficient, well-crafted code—and they’re willing to pay top dollar for it.

The Competitive Landscape for Tech Salaries

In the fast-paced world of technology, programming languages rise and fall in popularity as new ones emerge, specialized for unique tasks or optimized for performance. In recent years, languages like Clojure, Perl, and Zig have consistently ranked at the top in terms of salary, alongside established languages like Ruby. These high salaries are often a direct reflection of each language’s demand, the scarcity of skilled developers, and the specific value they offer to organizations.

For example, Clojure and Zig may not have the same mainstream appeal as JavaScript or Python, but they’re highly valued for specialized roles that require advanced performance or functional programming capabilities. This demand creates a smaller, competitive job market, where companies pay a premium for expertise that can help solve complex problems or deliver cutting-edge solutions.

Salaries in the tech industry can tell us a lot about the market forces at play. High compensation often signals that a technology requires deep expertise, is less commonly known, or has a significant impact on an organization’s efficiency or product.

In this competitive landscape, Ruby’s consistently high salaries suggest it remains indispensable to many organizations, particularly in fields like web development and startups. The continued willingness to invest in Ruby developers, even as newer languages emerge, speaks to Ruby’s staying power and the value it brings to projects that prioritize developer productivity and rapid iteration.

Ruby salary data

According to the Developer Survey conducted annually by the most respected programming resource, stackoverflow.

Stack Overflow’s annual Developer Survey is the largest and most comprehensive survey of people who code around the world.

2019

2020

2021

2022

2023

Take a look at the references section if you want to double check the data.

Ruby Salary Trends: 2019-2023

2019: 6th highest salary globally, at $75k, with a $15k gap from the highest (Clojure).
2020: 5th place with $71k, narrowing the gap to $5k from Perl, the highest-paid language.
2021: Returns to 6th at $80k, with a $15k gap from the top (Clojure).
2022: Climbs to 5th at $93k, with a $13k gap from the highest (Clojure).
2023: Reaches 4th with nearly $99k, narrowing the gap to $4k from the highest (Zig).

Data breakdown

Consistent High Ranking

Ruby’s steady position among the top 10 highest-paying technologies from 2019 to 2023 highlights its enduring value in the tech world.

Despite a rapidly changing landscape filled with emerging languages and tools, Ruby has consistently held strong, maintaining a rank between 4th and 6th place globally. This high ranking isn’t just a matter of coincidence—it reflects the steady demand for Ruby expertise across a variety of industries.

The fact that Ruby has remained highly paid over several years suggests a level of trust and reliance from companies, especially in sectors like web development, e-commerce, and tech startups, where Ruby on Rails has become a go-to framework for building robust applications quickly.

Businesses that rely on Ruby are often focused on developer productivity, maintainability, and the ability to bring applications to market smoothly.

This consistent ranking demonstrates that Ruby isn’t just a temporary trend; it’s a mature and reliable choice for companies who value efficiency, scalability, and developer satisfaction.

Steady Salary Increase

Ruby has seen a noticeable rise in average salaries over the past few years, reflecting its sustained demand and relevance in the tech industry. From 2019 to 2023, Ruby developer salaries steadily climbed, starting at $75k and reaching nearly $99k.

This consistent trajectory is a strong indicator that companies recognize and are willing to pay for Ruby’s unique benefits, especially as experienced Ruby developers remain highly valued across many sectors.

These salary increases aren’t just about inflation—they reflect the strategic importance of Ruby in areas like web application development, where speed and efficiency are necessary. Ruby’s ability to help teams build high-quality, scalable applications quickly makes it a favorite in industries where time-to-market and agility are essential.

As more companies see the value of Ruby’s productivity-focused design, demand for skilled developers continues to rise, and salaries follow suit.

For developers, this steady salary growth offers an encouraging outlook. Whether you’re new to Ruby or a seasoned expert, the market’s consistent investment in Ruby skills suggests that learning and mastering the language can lead to increasingly rewarding career opportunities. It’s a clear signal that the language remains valuable, even as new technologies emerge.

Narrowing Salary Gap with Top Technologies

One of the most striking trends in recent years is Ruby’s steady approach to the top of the tech salary charts. In 2019, the gap between Ruby developers and those working with the highest-paying technology was around $15,000.

Fast-forward to 2023, and that gap has shrunk to just about $4,000. This narrowing gap tells an interesting story about Ruby’s place in the tech landscape: it’s a language that continues to grow in competitiveness and value, even as new, highly specialized languages enter the market.

For developers, this trend is promising. It indicates that Ruby, despite being a more established language, remains as financially rewarding as many newer alternatives. This speaks to its adaptability, robust ecosystem, and the strong developer community that continues to advance the language.

Companies clearly recognize that hiring skilled Ruby developers brings long-term value, and as they compete to attract top talent, salaries have risen accordingly.

Ultimately, this narrowing gap highlights that Ruby is a strategic choice for developers seeking both high compensation and diverse opportunities, affirming that it’s not only relevant but also competitive at the highest levels in today’s job market.

Why Ruby?

Developer Productivity and Happiness

One of Ruby’s core philosophies is to make coding a pleasant and productive experience. The language was designed with simplicity and readability in mind, allowing developers to write clear, concise code that’s easy to understand and maintain.

This focus on developer happiness has made Ruby especially popular in environments that prioritize rapid iteration, such as tech startups and agile development teams.

By reducing the cognitive load on developers and speeding up the coding process, Ruby allows teams to focus on building impactful features rather than getting stuck in syntax or overly complex structures.

Loyal community

A key factor behind Ruby’s success is its loyal community and the extensive resources this network has cultivated over the years. Ruby has been around long enough to develop a vast ecosystem filled with powerful libraries, versatile plugins, and thorough documentation.

This community-driven support system provides developers with everything they need to succeed—from robust tools and educational content to networking opportunities and collaborative projects, such as Meetups and Tropical Rails in Brazil.

One of Ruby’s greatest assets is the continued popularity of Ruby on Rails, which has been widely adopted for building reliable, scalable applications. The Ruby community actively contributes to Rails and the language itself, consistently introducing updates, best practices, and new features.

This collaborative environment attracts both new talent and experienced developers, while offering companies confidence in the language’s long-term viability and stability.

For businesses, hiring Ruby developers means accessing not only technical expertise but also a community that has made Ruby development faster, easier, and more reliable.

References

2023 Top paying technologies

2022 Top paying technologies

2021 Top paying technologies

2020 Top paying technologies

2019 Top paying technologies

Done

Let's network

How to undo a git pull command

Alexandre Calaça — Fri, 08 Nov 2024 14:49:59 +0000

Situation

Sometimes in Git, we may want to go back to a previous state in our repository. This could be due to an unintended change, a deleted branch, or simply the need to return to an earlier version.

In my situation, I wanted to revert a git pull command.

Git’s reflog command is really valuable for this, as it allows us to see the recent history of the repository, including actions like checkout, reset, and other state changes that wouldn’t normally appear in a git log command.

Let's move on.

View the history of changes

The first step is to view the reflog. This shows a history of all the changes and commits you’ve made, even those that might not be reflected in the regular git log.

git reflog

Expected output

Each entry in the reflog output displays:

The commit hash, which uniquely identifies each commit.
The type of action taken (e.g., checkout, commit, reset).
A brief description of the action.

The reflog provides an easy way to find the exact commit we want to revert to or reset.

In this example, we’ll identify the commit hash for our target commit.

Identify the commit

After running git reflog, look for the commit hash you want to reset to.

git reflog

Expected output

I want to remove the most recent commit, so, I need to identify one commit before that.

Reset the head

To move the state of your repository back to this specific commit, you’ll use git reset with the --hard option.

The --hard option tells Git to reset the staging area and working directory to match the specified commit.

Pattern

git reset --hard <commit-hash>

IN my situation, the code would look something like this

git reset --hard 5fp725df74

Expected output
After running this command, Git should confirm the reset, and your repository will be in the exact state it was at the specified commit:

Confirm the reset

git reflog

Expected output
The reset will be visible, showing that your HEAD has been moved to the selected commit

Check your log

To verify that your repository has been reset correctly, use the git log command. This command shows the commit history, which should now reflect the state of your repository after the reset.

git log

The git log output should now show the recent history up to the commit you reset to, with any subsequent commits excluded:

Done

error Command "webpack" not found

Alexandre Calaça — Wed, 06 Nov 2024 02:59:49 +0000

Situation

After setting up my Rails 6 application and running rails server for the first time, I navigated to http://localhost:3000 to check if everything was working.

However, I immediately encountered an error screen, and the server log displayed the following messages:

It seemed like Webpacker was trying to compile my JavaScript assets but couldn’t complete the process because it couldn't find webpack.

Error

error Command "webpack" not found.

  Rendered layout layouts/application.html.erb (Duration: 930.4ms | Allocations: 11999)
Completed 500 Internal Server Error in 934ms (ActiveRecord: 0.0ms | Allocations: 14691)



ActionView::Template::Error (Webpacker can't find application.js in /home/athanasius/www/mind_dash/public/packs/manifest.json. Possible causes:
1. You want to set webpacker.yml value of compile to true for your environment
   unless you are using the webpack -w or the webpack-dev-server.
2. webpack has not yet re-run to reflect updates.
3. You have misconfigured Webpacker's config/webpacker.yml file.
4. Your webpack configuration is not creating a manifest.
Your manifest contains:
{
}
):

Explanation

The error you're seeing indicates that Webpacker is failing to compile your assets because it can't find the webpack command.

This issue typically arises when webpack isn’t properly installed or configured in your Rails 6 application.

Solution

To resolve issues with Webpacker, first ensure that webpack and webpack-cli are installed in your project.

At least, this is how I solved my issue.

Install webpack and dependencies

yarn add webpack webpack-cli

Once the installation completes, you should see output indicating that webpack and webpack-cli have been successfully added to your node_modules directory.

Rebuild webpacker

After installing webpack, it’s important to rebuild Webpacker to ensure all configurations are updated.

This command will generate or update files required for Webpacker to function correctly with Rails:

rails webpacker:install

This command’s output should confirm that Webpacker has been installed and configured. It typically generates a message indicating that Webpacker's configuration files have been successfully created or updated.

Run the server again

Done

How to Set Up SSH Keys for GitHub on PopOs or Ubuntu: A Beginner's Guide

Alexandre Calaça — Tue, 05 Nov 2024 02:42:24 +0000

Introduction

In this guide, you’ll learn how to generate an SSH key and set it up with GitHub. SSH keys provide a secure way to access GitHub without needing to repeatedly enter your password, making your workflow faster and more secure.

Solution

Generate a new SSH key

To generate a new SSH key, run the following command in your terminal:

ssh-keygen -t ed25519 -C "any comment"

This command uses the ed25519 algorithm, which is considered both secure and efficient. Replace "any comment" with something descriptive, like your email or a short label.

This comment will help you identify your key later, especially if you manage multiple SSH keys.

Output

Enter file

You’ll be prompted to choose where to save the key file. By default, the SSH key is saved in the ~/.ssh directory with a generic name like id_ed25519.

If you’d like to name the key something else (e.g., pop_os_athanasius), you can enter the file path here.

If you want to keep it as the default, simply press Enter.

In this example, we’ll name it /home/athanasius/.ssh/pop_os_athanasius.

Output

Enter passphrase

You’ll be prompted to enter a passphrase to protect your key. Using a passphrase is recommended for added security.

However, if you prefer to leave it blank, just press Enter twice. Keep in mind that without a passphrase, anyone with access to your machine can use this key.

In this example, we’ll leave it blank for simplicity.
Output

Verify the key generation

Once the key generation process is complete, you should see a confirmation message showing the key’s fingerprint. This unique identifier verifies the key was created successfully.

View the public key

To connect your SSH key with GitHub, you’ll need to add the public key to your GitHub account. To display your public key in the terminal, run:

cat ./.ssh/pop_os_athanasius.pub

Adding the SSH Key to GitHub

With your SSH key ready, it’s time to add it to GitHub for secure access.

Access GitHub Settings

Navigate to GitHub, log in, and go to Settings. You can find this option in the drop-down menu under your profile icon.

Open the SSH and GPG Keys Section

In the Settings menu, find and click on SSH and GPG keys from the sidebar. This section is where you’ll add new SSH keys to your GitHub account.

Add a New SSH Key

Click New SSH key. You’ll be prompted to enter a title and paste your key.

Save the key

Click Add SSH key to save it to your GitHub account. You may be prompted to confirm this action with your GitHub password.

Check connection

With your key added, let’s test the connection to GitHub. This step verifies that everything is configured correctly.

Run the following command:

ssh -T git@github.com

The first time you connect to GitHub via SSH, you may see a message like this:

The authenticity of host 'github.com (20.201.28.151)' can't be established.
ED25519 key fingerprint is SHA256:+AiB3wcvD6FuJGhblZimn/zMBA0zZNSvHakb4evDOkU.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])?

Type yes

The authenticity of host 'github.com (20.201.28.151)' can't be established.
ED25519 key fingerprint is SHA256:+AiB3wcvD6FuJGhblZimn/zMBA0zZNSvHakb4evDOkU.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.
Hi alexcalaca! You've successfully authenticated, but GitHub does not provide shell access.

Type yes and press Enter to continue. GitHub will now be added to your list of known hosts.

Success

If you see the message confirming your authentication, congratulations! You’ve successfully set up SSH for GitHub, which means you can now use SSH-based commands to interact with your repositories.

Hi alexcalaca! You've successfully authenticated, but GitHub does not provide shell access.

Output

Done

Installing the best terminal emulator on Pop!_OS 22.04: Terminator

Alexandre Calaça — Tue, 05 Nov 2024 01:34:40 +0000

Terminator

Terminator is a popular terminal emulator for Linux, especially favored by power users and developers who work extensively with the command line. Terminator’s main attraction lies in its flexibility and advanced features like split screens, tabs, and extensive keyboard shortcuts. These features make it a versatile tool for managing multiple sessions and running commands concurrently.

It's available in the software repositories of many Linux distributions and can be installed using package managers like APT (for Debian/Ubuntu-based systems) or YUM (for Red Hat/Fedora-based systems).

Let's get down to business

Shall we?

Check your OS (optional)

If you’re unsure about your operating system’s details, you can run a few simple commands to check. These commands give you information about the OS version, kernel, and distribution, which can be useful if you’re following specific installation instructions.

Run these commands in your terminal:

uname -a         # Shows the system kernel version and architecture
hostnamectl      # Displays OS and hostname details
lsb_release -a   # Provides distribution-specific information
cat /etc/os-release # Shows detailed OS version and ID

Output

Knowing your OS version can be helpful when troubleshooting or verifying that Terminator is compatible with your system.

IN this article, we'll focus on PopOs.

Update package info

Before installing any new software, it’s good practice to update your system’s package list to ensure you’re getting the latest version of any software. This step refreshes the local list of available packages and their versions from the configured software repositories.

To update your system’s package information, run:

sudo apt-get update

Running sudo apt-get update is an important step before installing or upgrading packages on your system because it ensures that you have the most up-to-date information about available packages.

Without updating the package index, you might not see the latest versions of software or be able to install new packages that have been added to the repositories since the last update.

Install Terminator

Now that the package information is updated, you’re ready to install Terminator.

sudo apt install terminator

Output

The installation process will download and set up Terminator on your system. You may be prompted to enter your user password to authorize the installation.

verify installation

After installation, it’s always a good idea to verify that Terminator has been correctly installed. This can be done by checking its version and confirming its location in the system’s file paths.

Run the following commands to verify:

terminator --version  # Displays the installed version of Terminator
which terminator      # Shows the location of the Terminator executable

Output

If both commands return results without errors, Terminator is successfully installed and ready to use.

Run

With everything set up, you can launch Terminator by simply typing:

terminator

Output

When Terminator opens, you’ll see a simple interface that allows you to split the terminal screen horizontally or vertically, add new tabs, and customize each window. You can create multiple terminals in one window and manage each independently, making it easy to multitask without switching between different terminal windows.

Done

You’re now ready to use Terminator. With its advanced features, Terminator can help make managing multiple command-line tasks simpler and more efficient.

Celebrate

BCrypt::Errors::InvalidHash (invalid hash)

Alexandre Calaça — Mon, 28 Oct 2024 17:35:12 +0000

Introduction

Encountering errors while resetting your database or managing password fields can be a challenging part of Rails development.

In this simple article, I’ll walk through the process of resolving the BCrypt::Errors::InvalidHash error, which occurred after recreating a user password. Here’s what happened, how I tested possible solutions, and the final approach that resolved the issue.

Context

After running rails db:drop to drop the database and recreate it, I had to re-enter user data, including setting a new password. However, when attempting to assign a password to the encrypted_password field directly in the User model, I encountered the following error:

BCrypt::Errors::InvalidHash (invalid hash)

This error typically occurs when the value stored in encrypted_password is not a valid BCrypt hash. In Rails, if you're using has_secure_password, BCrypt expects a hashed value in encrypted_password. Assigning a plain-text password directly to encrypted_password without hashing causes this mismatch.

Inital setup

After the database reset, I attempted to assign a password by manually setting encrypted_password:

user = User.new(email: "user@example.com")
user.encrypted_password = "newpassword123"  # Incorrect approach
user.save

Solution

To resolve the error, I needed to ensure the password was properly hashed using BCrypt. Instead of manually assigning a value to encrypted_password, I updated the user’s password attribute directly and let BCrypt handle the hashing.

Here’s the code that worked:

User.where(email: "email@example.com").first
hashed_password = BCrypt::Password.create("newpassword#0")
user.update_column(:encrypted_password, hashed_password)

Explanation

In this solution, I used BCrypt::Password.create to hash the plain-text password "newpassword#0", then directly updated the password attribute.

This approach allowed BCrypt to generate a valid hash for encrypted_password, avoiding the BCrypt::Errors::InvalidHash error. By assigning the hashed password to password, Rails automatically handled storage in the correct format, fixing the issue.

DEV Community: Alexandre Calaça

How to undo a specific pushed commit

Navigate to Your Repository:

Check the Status:

Find the Commit Hash:

Revert the Commit:

Push the Reverted Changes

Double check

Done

Final message

MBA em Desenvolvimento de Software Avançado com foco em Ruby on Rails

Vaga Desenvolvedor Backend - Ruby on Rails - AGROS

Descrição da Vaga

Requisitos Desejáveis

Regime de Contratação

PCD

Benefícios

Vaga Desenvolvedor Jr - Ruby on Rails - Híbrido

Descrição da vaga

Contratação CLT + Benefícios:

Responsabilidades e atribuições

Requisitos e qualificações

Etapas do processo

How to Switch Your Rails Application Database from PostgreSQL to SQLite

Introduction

Update the Gemfile

Update the database configuration

Update dependencies

Run dependencies

Re-create the structure

Test your application

Conclusion

Done

Let's network

How to clean up repetitive keys in .html.erb templates?

Introduction

Situation

Solution

Sample file

The prefix approach

Make it happen

Why the `prefix approach

Done

Let's network

Ruby: One of the top 5 highest-paying technologies, according to Stack overflow

Introduction

The Competitive Landscape for Tech Salaries

Ruby salary data

Ruby Salary Trends: 2019-2023

Data breakdown

Consistent High Ranking

Steady Salary Increase

Narrowing Salary Gap with Top Technologies

Why Ruby?

Developer Productivity and Happiness

Loyal community

References

Done

Let's network

How to undo a git pull command

Situation

View the history of changes

Identify the commit

Reset the head

Confirm the reset

Check your log

Done

error Command "webpack" not found

Situation

Error

Explanation

Solution

Install webpack and dependencies

Rebuild webpacker

Run the server again

Done

How to Set Up SSH Keys for GitHub on PopOs or Ubuntu: A Beginner's Guide

Introduction

Solution

Generate a new SSH key

Update the `Gemfile`

The `prefix` approach