MrEromz

Using a CDN for Tailwind CSS directly in your HTML file isn't the best practice for production. Here's a breakdown of the problems and a recommended solution using a build process:

Problems with Direct CDN Inclusion:

• Performance: Fetching Tailwind CSS from a CDN adds an extra HTTP request to your page load, slowing down initial rendering.
• Bundle Size: The entire Tailwind CSS library is included in your HTML, adding unnecessary weight to your page.
• Customization: It's not ideal for customizing Tailwind's defaults, as you'll need to modify the CDN's version directly.
• Cache Busting: You might not have control over the caching of the CDN, leading to issues with updates.

Best Practices: Build Process (with Vite or Parcel)

MrEromz

Moved to git repository: https://github.com/denji/jetbrains-cleanup-backup

Quick uninstall JetBrains settings:

curl -sL https://gist.github.com/denji/9731967/raw/jetbrains-uninstall.sh | bash -s

Quick backup JetBrains settings:

curl -sL https://gist.github.com/denji/9731967/raw/jetbrains-backup.sh | bash -s

MrEromz

#!/usr/bin/sh

rm -rf "$HOME/Library/Preferences/WebIde40"
rm -rf "$HOME/Library/Caches/WebIde40"
rm -rf "$HOME/Library/Application Support/WebIde40"
rm -rf "$HOME/Library/Logs/WebIde40"

MrEromz

When it comes to databases and AWS VPC, best practice is to place your database in private subnet. By definition, private subnet in AWS is not reachable from the Internet because no Internet gateway is attached to private subnet. This is the way you protect your data. This kind of configuration is good for security but bad for data management.

How can you easily access and manage your secured data?

There are two basic ways to acees it.

1. Access postgres RDS from bastion host. There are following requirements for this.