Taken from StackExchange
Thanks to LangLangC
For temperature and other improvements see https://gist.github.com/cdleon/d16e7743e6f056fedbebc329333d79df
#!/bin/bash | |
# Function to display usage information | |
usage() { | |
echo "Usage: $0 /path/to/input.mp4 [ /path/to/output_directory ]" | |
exit 1 | |
} | |
# Check if at least one argument (input file) is provided | |
if [ $# -lt 1 ]; then |
Taken from StackExchange
Thanks to LangLangC
For temperature and other improvements see https://gist.github.com/cdleon/d16e7743e6f056fedbebc329333d79df
# --------------------------------------------------------------------------- | |
# | |
# Description: This file holds all my BASH configurations and aliases | |
# | |
# Sections: | |
# 1. Environment Configuration | |
# 2. Make Terminal Better (remapping defaults and adding functionality) | |
# 3. File and Folder Management | |
# 4. Searching | |
# 5. Process Management |
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso
Industry | ||
---|---|---|
Accounting | ||
Airlines/Aviation | ||
Alternative Dispute Resolution | ||
Alternative Medicine | ||
Animation | ||
Apparel/Fashion | ||
Architecture/Planning | ||
Arts/Crafts | ||
Automotive |
You are an expert in Laravel, Inertia.js, React and Tailwind CSS, with a strong emphasis on Laravel and PHP best practices.Key Principles- Write concise, technical responses with accurate PHP examples.- Follow Laravel best practices and conventions.- Use object-oriented programming with a focus on SOLID principles.- Prefer iteration and modularization over duplication.- Use descriptive variable and method names.- Favor dependency injection and service containers.PHP and Laravel Core- Use PHP 8.3+ features when appropriate (e.g., typed properties, match expressions).- Follow PSR-12 coding standards.- Use strict typing: declare(strict_types=1);- Utilize Laravel's built-in features and helpers when possible.- Follow Laravel's directory structure and naming conventions.- Use lowercase with dashes for directories (e.g., app/Http/Controllers).- Implement proper error handling and logging: - Use Laravel's exception handling and logging features. - Create custom exceptions when necessary. - Use try-catch blocks for e |
<?php | |
namespace App\Filament\PageTemplates; | |
use Filament\Forms\Components\Repeater; | |
use Filament\Forms\Components\RichEditor; | |
use Filament\Forms\Components\TextInput; | |
final class Faq | |
{ |
<?php | |
/* | |
* NOTES: | |
* | |
* - This was designed for my personal use and could be more robust. | |
* - Make sure to update the tables you want to import into. | |
* - Make sure to update the website url you want to import from. | |
* - Customize as needed. I had very few posts and no media. | |
* | |
*/ |
{ | |
"name": "my_vendor_name/my_package", | |
"description": "My Package Description", | |
"license": "GPL-3.0", | |
"autoload": { | |
"classmap": [ // search these directories for classes | |
"lib/" | |
] | |
}, | |
"repositories": { |