diogogpinto

I have been utilizing artificial intelligence to enhance and optimize my codebases. After evaluating various models, applications, and editors, I find the claude.ai interface with a Pro Account to be the most effective. Here’s the approach I’ve developed to achieve optimal results:

This gist contains a carefully crafted prompt and a script designed to convert your entire Laravel codebase (excluding the resources folder, which can be easily added if needed) into a TXT file with the following structure:

<File Start: ./path/filename.extension> Content of file <End File: ./path/filename.extension>

To implement this method:

jonerickson

name: Deploy Application

env:
  SIDECAR_APP_NAME: ${{ secrets.SIDECAR_APP_NAME }}
  SIDECAR_ACCESS_KEY_ID: ${{ secrets.SIDECAR_ACCESS_KEY_ID }}
  SIDECAR_SECRET_ACCESS_KEY: ${{ secrets.SIDECAR_SECRET_ACCESS_KEY }}
  SIDECAR_REGION: ${{ secrets.SIDECAR_REGION }}
  SIDECAR_ARTIFACT_BUCKET_NAME: ${{ secrets.SIDECAR_ARTIFACT_BUCKET_NAME }}
  SIDECAR_EXECUTION_ROLE: ${{ secrets.SIDECAR_EXECUTION_ROLE }}
  VAPOR_API_TOKEN: ${{ secrets.VAPOR_API_TOKEN }}

abelcallejo

Creating a starter kit for Laravel

You are probably wondering how Laravel made some starter kits to be easily installable using just the following commands:

composer install laravel/breeze     # Quickly integrates the starter kit to the composer environment
php artisan breeze:install          # Quickly integrates the starter kit to the Laravel environment

If you want to build a project with the same installation setup, you are on the right track. This documentation is all about doing exactly just that. Without further ado, let's just jump right into it!

shinsenter

UPDATE:

2023/12/18: This script has been improved and moved to the following repository:

https://github.com/shinsenter/docker-squash

---

Make your Docker images smaller by reducing the number of layers

shinsenter

Beginning

There are many approaches to implementing a reuse of a common preset for Docker services for multiple environments, such as production and local environments.

This makes it possible to ensure the highest consistency for different environments with the same code-base. Implementing reuse of docker compose options also makes it easier to manage them.

I found on github a project called serversideup/spin. They took an approach using a feature called Docker overrides, to change some properties of common services for different environments.

After reading through their documentation, I realized that there are a few real-life cases where this project can not implement (or is difficult to archive).

SumitBando

Original AlpineJS	Svelte Translation	Explanation

danieljpalmer

<?php
/**
 * In your Livewire model for the list of items
 */

class ItemList extends Component
{

    // rest of component

tanthammar

<?php

namespace App\Traits;

trait HasLinks
{

    // $model->links = array
    public function getLinksAttribute(): array
    {

LukeMathWalker

image: "rust:latest"

default:
  before_script:
    - rustc --version 
    - cargo --version

stages:
  - test

LukeMathWalker

name: Security audit
on:
  schedule:
    - cron: '0 0 * * *'
  push:
    paths:
      - '**/Cargo.toml'
      - '**/Cargo.lock'
jobs:
  security_audit: