List of helpful shortcuts for faster coding
If you have any other helpful shortcuts, feel free to add in the comments of this gist :)
Indicating the project status in your README is a great way to communicate the current state of your project to potential collaborators, recruiters, or users. You can use a "Project Status" section near the top of your README to make this clear. Here’s how you can do it:
Including a badge is a common way to display project status. You can generate badges using services like shields.io. Here’s an example:

providers.tf
Description: The providers.tf
file is used to configure and declare provider settings in Terraform. Providers enable Terraform to interact with cloud platforms (e.g., AWS, Azure, GCP) or other services. This file specifies provider versions, regions, and authentication methods.
variables.tf
Description: The variables.tf
file defines input variables for Terraform configurations. These variables allow parameterization of values like resource names, regions, or instance types, making configurations more reusable and dynamic.
outputs.tf
Description: The outputs.tf
file is used to expose the results of a Terraform run. It outputs values, such as IP addresses, URLs, or resource attributes, for use by other configurations, tools, or workflows.
Both .gitkeep
and .keep
can be used to keep an empty directory in version control. However, the difference lies in how Git handles them.
.gitkeep
is a file that tells Git to keep the directory it's in as a versioned entity. When you commit a .gitkeep
file to a Git repository, Git will keep the directory it's in, even if it's empty.
.keep
is a file that tells Git to keep the directory it's in as a versioned entity, but it's not as widely supported as .gitkeep
. While both files achieve the same purpose, some Git versions may not recognize .keep
as a valid file for keeping directories.
In general, it's recommended to use .gitkeep
instead of .keep
to ensure that your empty directories are kept in version control across different Git versions and platforms.
When using Terraform with Git, it's common to associate a Terraform workspace with a specific Git branch. This allows you to manage different environments and configurations for each branch.
Here's a general workflow:
git branch dev
.terraform workspace new dev
to create a new workspace named "dev".terraform workspace select dev
to switch to the "dev" workspace.git add
and git commit
.To set up dbt (Data Build Tool) for using Postgres locally, you need to: