Ruby on Rails

Configuración de PATH

export PATH="$PATH:/usr/share/rvm/bin/:/opt/Android/Sdk/platform-tools/:/home/adrian/.gem/ruby/2.7.0/bin"

Así é como teño actualmente o .bashrc.

• /usr/share/rvm/bin/ 👉 TODO: Teño que revisar este directorio, creo que xa non existe
• /home/adrian/.gem/ruby/2.7.0/bin 👉 É importante ter esta ruta para poder executar as gemas executables. En caso de non tela podemos obter o seguinte warning en algúns casos:

Jekyll

Jekyll * Simple, blog-aware, static sites

Jekyll

Testing

Revisar estos posts:

RSpec vs Test::Unit in Rails

Difference between Unit::Test versus Rspec

What not to test in Rails?

Posibles problemas

Increasing the amount of inotify watchers

listen/README at master · guard/listen

Por que non se deben modificar migracións

Editing Existing Rails Migrations is a good idea?

Deshacer migracións (rollbacks) de migracións en específico

How to rollback just one step using rake db:migrate

Ver status de migrations (pendentes e executadas):

rake db:migrate:status

# Or (rails >= 5)

rails db:migrate:status

Roll back the most recent migration:

rake db:rollback

Roll back the n most recent migrations:

rake db:rollback STEP=n

Here's some more:

• rake db:migrate - Run all migrations that haven't been run already
• rake db:migrate VERSION=20080906120000 - Run all necessary migrations (up or down) to get to the given version
• rake db:migrate RAILS_ENV=test - Run migrations in the given environment
• rake db:migrate:redo - Roll back one migration and run it again
• rake db:migrate:redo STEP=n - Roll back the last n migrations and run them again
• rake db:migrate:up VERSION=20080906120000 - Run the up method for the given migration
• rake db:migrate:down VERSION=20080906120000 - Run the down method for the given migration

Caché en local

Ao activar caché en local pode dar lugar a excepcións cando se fan cambios no código sen reiniciar o servidor:

Rails.cache.fetch exception: TypeError ( can't be referred to)

Migracións

change method

The change method is the primary way of writing migrations. It works for the majority of cases, where Active Record knows how to reverse the migration automatically.

👉 List of supported Methods

If you're going to need to use any other methods, you should use reversible or write the up and down methods instead of using the change method.

Never rescue Exception

If you rescue Exception, you will rescue every exception, including some like:

• SignalException::Interrupt - If you rescue this, you can't exit your app by hitting control-c.
• ScriptError::SyntaxError - Swallowing syntax errors means that things like puts("Forgot something) will fail silently.
• NoMemoryError - Wanna know what happens when your program keeps running after it uses up all the RAM? Me neither.

Rescue StandardError Instead and Custom Exceptions Should Inherit from StandardError.

👉 The Honeybadger Developer Blog