Fueling Curiosity, One Insight at a Time

test your gem locally before publishing.
• STEP 1 - cd into your gem directory and run gem build your-gem.gemspec
• STEP 2 - in the same directory then run gem install ./your-gem-<version>.gem (<version> will be replaced by the current version of your gem)
• STEP 3 - Now cd into your project where you want to install this gem.
• STEP 4 - Open Gemfile and add gem 'your-gem', path: '/path/to/your-gem' (Replace /path/to/your-gem with the actual path to your gem.
#ruby-gems , #rails
TIP: you can get your path by running pwd in your terminal where you have opened your gem file.

Fly Secret Value Displaying Feature:

We can able to see Fly secrets values from terminal . From the Dashboard of fly we can't able to the secret value. But from the terminal we can able to the see secret value .
For that we have use below command:
• First Go the project in terminal and enter the fly ssh console. It redirects you to the fly application in remote.
• Then you can see the what value you want using echo command. Ex: echo $DATABASE_URL . After entered like this it will display what is the value of the key. Likewise you can place what are ever key want to see.

for tracking emails for analytics purpose sent from mailgun we can use o:tag parameter along with parameters like subject and domain
https://www.mailgun.com/blog/email/tags-explained-gaining-useful-insights-from-email-segmentation/

To delete a Docker image we can use a command docker rmi [IMAGE_ID or REPOSITORY:TAG] and ,
To remove all dangling images that consume disk space , can use docker image prune

forms in rails 7 are now submitted with turbo_stream format.
for eg: from the logs:
Started POST "/books" for 127.0.0.1 at 2024-02-16 14:44:16 +0530
Processing by BooksController#create as TURBO_STREAM

push a new version of your gem to https://rubygems.org|rubygems.org using bundle exec rake release

To remove rvm and its traces, you can use the rvm command itself:
rvm implode
This command will remove all traces of rvm from your system.

difference between oauth/v2/authorize & openid/connect/authorize
I am taking the example in context of Slack .
1. OAuth 2.0 (/oauth/v2/authorize):
• Usage: When a third-party application needs to access a user's resources in Slack, it uses the /oauth/v2/authorize endpoint.
• Process: The user is prompted to grant the application permission to access their resources. Upon consent, Slack returns an authorization code to the application. This code is then exchanged for an access token, which the application uses to access the user's resources on Slack.
• Focus: Purely on granting access to resources (authorization).
2. OpenID Connect (/openid/connect/authorize):
• Usage: When an application not only needs to access resources but also verify the identity of the Slack user, it uses the /openid/connect/authorize endpoint.
• Process: Similar to OAuth 2.0, but in addition to granting access, this process authenticates the user and returns an ID token along with an authorization code. The ID token contains claims about the user's identity, which can be used by the application to verify who the user is.
• Focus: On both verifying user identity (authentication) and granting access to resources (authorization).

Launching an NGINX pod imperatively (directly from the command line) can be done using the
kubectl run nginx-pod --image=nginx --restart=Never

Ensure that Docker Desktop is running before executing the docker build command.