TILs - Fueling Curiosity, One Insight at a Time

At Codemancers, we believe every day is an opportunity to grow. This section is where our team shares bite-sized discoveries, technical breakthroughs and fascinating nuggets of wisdom we've stumbled upon in our work.

Published
Author
user-image
Sagar Ghorse
while integrating sentry with gitlab ip whitelisting needs to be done on gitlab server (self-hosted)
#devops #sentry#gitlab
Published
Author
user-image
Soniya Rayabagi
The kubectl cordon NODE_NAME command is used in Kubernetes to mark a node as unschedulable, meaning no new pods will be scheduled onto that node. Existing pods on the node will continue to run unless explicitly terminated or moved.
#devops #kubernetes
Published
Author
user-image
Nisanth
Debugging Kubernetes pod on helm
helm upgrade unleash-app-toggle . --debug
Adding --debug can provide more insight if the error persists, showing exactly what values are being passed to each template.
#devops #kubernetes #helm
Published
Author
user-image
Nisanth
Avoid Using Double Quotes for Environment Variables
When configuring the PostgreSQL user and database names in a Helm values.yaml file, I initially wrapped the values in double quotes. This led to a frustrating issue where I couldn’t connect to the database, receiving errors that the role did not exist. The double quotes were being interpreted literally, causing mismatches in authentication.
Solution: I removed the double quotes around the environment variables in my Helm chart and reapplied the configuration. This corrected the problem, and I was then able to connect successfully to the database.
#devops #postgres #env
Published
Author
user-image
Sagar Ghorse
create the redis cluster from existing backup we can use snapshot_name = <name of your backyp >
#devops #redis #Terraform
Published
Author
user-image
Nisanth
To find the number of pods that exist in the “dev” environment (env), you can use the
kubectl get pods --selector=env=dev
#devops #kubernetes
Published
Author
user-image
Sachin Kabadi
System Analyst
#nextJs #TypeScript
useEffect is a hook that allows you to perform side effects in function components.

Code

import React, { useState, useEffect } from 'react';

function MyComponent() {
  const [count, setCount] = useState(0);

  // This effect will run only when the count state changes
  useEffect(() => {
    document.title = `You clicked ${count} times`;
  }, [count]); // Only re-runs when count changes

  return (
    <div>
      <p>You clicked {count} times</p>
      <button onClick={() => setCount(count + 1)}>
        Click me
      </button>
    </div>
  );
}

export default MyComponent;


In the above example:
• We have a component MyComponent with a state variable count and a button to increment it.
• Inside the component, we use the useEffect hook to update the document title with the current count after each render.
• We pass [count] as the second argument to useEffect, which means the effect will only run when the count state changes. This is because we want to update the document title only when the count changes, not on every render.
Published
Author
user-image
Sachin Kabadi
System Analyst
#nextJs #TypeScript
Function Argument Deconstructing: Deconstructing function arguments can make your code cleaner and more readable.

Code

// Before deconstruction 
const BlogPost = (props) => { 
  const { title, content, author } = props; 
  // Render blog post using props
  return (
      
          {props.title}
          {props.content}
          Written by: {props.author}
      
  );
}; 

// After deconstruction 
const BlogPost = ({ title, content, author }) => { 
  // Render blog post with title, content, and author 
  return (
      
          {title}
          {content}
          Written by: {author}
      
  );
};

Published
Author
user-image
Soniya Rayabagi
CMD-SHIFT-L is a great productivity booster for VS Code. Lets you select all instances of the current selection and edit with multiple cursors.
#VSCodetip #ProductivityHack
Published
Author
user-image
Mahesh Bhosle
DevOps Engineer
Terraform alias is a feature that allows you to manage resources across multiple regions more efficiently. It enables you to define different configurations for resources in various regions while using the same Terraform codebase.
Here's a simple example to illustrate how to use Terraform alias for multiple regions:

Code

provider "aws" {
  alias  = "us_east"
  region = "us-east-1"
}

provider "aws" {
  alias  = "us_west"
  region = "us-west-1"
}
resource "aws_instance" "example" {
  provider      = aws.us_east
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}

resource "aws_instance" "example_west" {
  provider      = aws.us_west
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}


In this example, we define two different AWS providers with aliases us_east and us_west, representing the US East and US West regions, respectively. Then, we create instances using these providers, specifying the region-specific provider for each instance. This allows Terraform to manage resources in different regions using the same configuration file.
#terraform #iac

Showing 25 to 27 of 82 results

Ready to Build Something Amazing?

Codemancers can bring your vision to life and help you achieve your goals