Abhinay Kumar abhinaykumar

<!-- ERROR -->
Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

Change your database RDS instance security group to allow your machine to access it.
- Add your ip to the security group to acces the instance via Postgres.
Make a copy of the database using pg_dump
- $ pg_dump -h <public dns> -U <my username> -f <name of dump file .sql> <name of my database>
- you will be asked for postgressql password.
- a dump file(.sql) will be created
Restore that dump file to your local database.
- but you might need to drop the database and create it first
- $ psql -U <postgresql username> -d <database name> -f <dump file that you want to restore>

the database is restored

Step-by-step guide: Get your FB Lead on your Webhook

This gist was created in 2023 and is inspired from tixastronauta and eladnava tutorial.

The Facebook API changes frequently. As a result, this guide might not be accurate.

1 - Create an App

Sign up for Facebook Developer access if you haven't already, from the same account as your Facebook Ads advertising account.

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.

	class Http
	class << self
	def send_request(url, options = {}, verb = :get)
	headers = options[:headers]
	headers = headers.present? ? default_headers.merge(headers) : default_headers
	body = options[:body].presence
	body = body.to_json if headers['Content-Type'] == 'application/json'
	query = options[:query].presence

	payload = verb == :get ? query : body

	{
	"facebook.com": "<i class='fa-brands fa-facebook-f'></i>",
	"twitter.com": "<i class='fa-brands fa-twitter'></i>",
	"instagram.com": "<i class='fa-brands fa-instagram'></i>",
	"linkedin.com": "<i class='fa-brands fa-linkedin-in'></i>",
	"snapchat.com": "<i class='fa-brands fa-snapchat'></i>",
	"tumblr.com": "<i class='fa-brands fa-tumblr'></i>",
	"pinterest.com": "<i class='fa-brands fa-pinterest-p'></i>",
	"reddit.com": "<i class='fa-brands fa-reddit-alien'></i>",
	"tiktok.com": "<i class='fa-brands fa-tiktok'></i>",

	# https://soravjain.com/digital-marketing-agencies-india/
	data = []
	email= nil
	address=nil
	phone=nil
	website=nil
	services=nil
	brands=nil
	doc.css("p").each do \|x\|
	if x.content.start_with?("Services")