jpalala

Undoing git stash

To undo a git stash, it depends on what exactly you mean by “undo”:

---

🔁 1. If you applied a stash and want to undo the changes:

git stash apply       # or git stash pop

jpalala

<?php

use Doctrine\ORM\EntityManagerInterface;
use DoctrineBatchUtils\BatchProcessing\SimpleBatchIteratorAggregate;

class LargeFileProcessor
{
    private EntityManagerInterface $entityManager;

    public function __construct(EntityManagerInterface $entityManager)

jpalala

>  yt-dlp -f "bestaudio/best" --extract-audio --audio-format m4a <you.tubeurl>

jpalala

#!/bin/bash
# config file looks like: 
## ```
# source=$PWD
# dest=/path/to/folder
### ```

# Check if .rsync file exists
CONFIG_FILE=".rsync"
if [[ ! -f "$CONFIG_FILE" ]]; then

jpalala

To fetch todos from a Notion database list using the Notion API, you'll need to follow these steps:

1. Create a Notion integration to get an API key
2. Share your database with the integration
3. Use the "Query a database" endpoint to fetch the list of tasks

Here's a step-by-step guide with code examples:

jpalala

Upload base64 encoded file to S3

1. Encrypt the .env file locally (on linux / mac):

   base64 your-env-file.env > encrypted-env-file.env

2. Upload the encrypted-env-file.env to S3 (via aws-cli)

Notes for Production

jpalala

<?php
use Illuminate\Support\Facades\Cache;
use Illuminate\Support\Facades\File;
use Illuminate\Support\Str;
use Illuminate\Support\Facades\Config;

// get data from an api that uses basic auth then decode it as a .env file
function get_features($url, $creds, $segment = []) {
  $ch = curl_init($url);
  curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/xml', $additionalHeaders));

jpalala

To show only running containers use the given command:

  docker ps

To show all containers use the given command:

 docker ps -a

jpalala

body {
  font: 22px/1.6 system-ui,sans-serif;
  margin: auto;
  max-width: 35em;
  padding: 0 1em;
}

img, video {
  max-width: 100%;
  height: auto;

jpalala

Yes, you can add tags to blog posts by creating a many-to-many relationship between posts and tags. This requires three tables:

1. posts: Table to store blog posts.
2. tags: Table to store tags.
3. post_tag: Pivot table to associate posts with tags.

---

Migration Code