Fueling Curiosity, One Insight at a Time

The docker-compose up command starts and runs all the services defined in a docker-compose.yml file, creating and starting containers.
docker-compose up -d command which starts the containers in the background and leaves them running (daemon processes) .

"terraform init -backend-config=backend.hcl" command initializes your Terraform directory and configures its backend according to the settings specified in the backend.hcl file, for managing infrastructure.
then , If you wish to attempt automatic migration of the state, use the command "terraform init -migrate-state"

Jenkins is a self-hosted CI/CD automation server, serving as an alternative to cloud-based services like GitHub Actions

Related to Auth0 and react-auth0 sdk
To add a custom parameter to the authentication endpoint of which auth0 interacts we can pass it like this in the object

authorizationParams: {
          screen_hint: "signup",
          ui_locales: "en",
          custom_param: "custom_param",
        },

authorizationParams object is used in methods loginWithRedirect, withAuthenticationRequired provided by @auth0/auth0-react

once the custom parameter is passed we can see it in /authorize endpoint when we open the Universal login or signup form from Auth0

If we want to take any custom actions based on this custom parameter we can access it in Auth0 post login custom actions

The docker build -f command is used to specify the name of the Dockerfile to use for building a Docker image. This flag allows you to specify the path to the Dockerfile that you want to use for building the image. However, if you have a Dockerfile with a different name or located in a different directory, you can use the -f flag followed by the path to the Dockerfile.

Storing Terraform State in S3 with Encryption and DynamoDB Locking , instead of Storing locally :
To improve security , you can configure Terraform to store its state file in an AWS S3 bucket with encryption and use DynamoDB for state locking. This setup prevents local state file risks, enables team access, and avoids state conflicts.

syntax : 

 terraform {
      backend "<BACKEND_NAME>" {
        [CONFIG...]
      }
}

example :

terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "state/production/terraform.tfstate"
    region         = "us-east-1"
    encrypt        = true
    dynamodb_table = "my-terraform-lock"
  }
}

act utility can be used to simulate GitHub Actions locally, for testing the GitHub workflows.

To install act on Mac: brew install act
To use the act navigate to the GitHub repo and use act -l to list all jobs
To run any particular job: act -j job_id
To run a job on any particular platform: act -j job_id -P

[To run the jobs locally, docker must be running on the system.]

square brackets [ ] indicate that the entire expression within them is optional
example : FROM [--platform=<platform>] <image> [AS <name>]
here , you can choose whether or not to include the --platform=<platform>

When ActiveJob is set to :inline it does not depends upon a scheduler anymore. Use perform_later as per your requirements and that will perform the job instantly.

If you face error as " Sprockets::Rails::Helper::AssetNotFound: The asset "tailwind.css" is not present in the asset pipeline " while running CI/CD pipeline or during deployment, then check whether you have add the the "app/assets/builds/*" in gitignore. Remove it and precompile assets again using "rake assets:precompile" or "rails assets:precompile". Make sure "tailwind.css" file exists in "app/assets/builds/" folder.