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.
:inline it does not depends upon a scheduler anymore. Use perform_later as per your requirements and that will perform the job instantly.
psql postgres if we face the below error:psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such file or directorybrew services start postgresql@15 Bootstrap failed: 5: Input/output error
Try re-running the command as root for richer errors.
Error: Failure while executing; `/bin/launchctl bootstrap gui/501 /Users/<user>/Library/LaunchAgents/homebrew.mxcl.postgresql@15.plist` exited with 5.brew services stop postgresql@15 rm -f /opt/homebrew/var/postgresql@15/postmaster.pid (apple sillicon install it at opt/homebrew)brew services start postgresql@15 brew services info postgresql@15config.hosts << "www.example.com"CIDR Block(Classless Inter-Domain Routing) pg_dump -h your-hostname -p your-port -U your-username -d your-database-name -f output-file.sql``
pg_dump with DROP table queries (clean dump):
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --clean -f output-file.sql
pg_dump for schema only:
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --schema-only -f output-file.sql
pg_dump for data only:
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --data-only -f output-file.sql
pg_dump for data only (no schema, INSERT commands only):
pg_dump -h your-hostname -p your-port -U your-username -d your-database-name --data-only --inserts -f output-file.sql`sidekiq-scheduler if your schedule file is named as sidekiq.yml make sure to add the schedule config entry.:scheduler: -> :schedule .:scheduler:
:schedule:
fetch_user_info_from_slack:
cron: '0 6 * * * Asia/Kolkata'
class: FetchSlackUserInfoJob
queue: 'default'
description: 'This job fetches user info from slack and updates the database'same AMI, you should first ensure that the AMI is available in both regions. If it's available in both regions (i.e.- "us-east-1" and "us-east-2") , you can proceed to use the same AMI for both instances. Otherwise, you should use two different AMIs.provider "aws" {
alias = "us-east-2"
region = "us-east-2"
}
resource "aws_instance" "instance" {
provider = aws.us-east-2
ami = "ami-id-1"
instance_type = "t2.micro"
}
provider "aws" {
alias = "us-east-1"
region = "us-east-1"
}
resource "aws_instance" "instance1" {
provider = aws.us-east-1
ami = "ami-id-2"
instance_type = "t2.micro"
}Git rebase is a command to reapply commits from one branch onto another, effectively rewriting the commit history.git rebase main to start.git add <file>.git rebase --continue.git push <remote> <branch-name> —-force.Showing 32 to 34 of 82 results
Codemancers can bring your vision to life and help you achieve your goals