akoepcke

<?php

namespace App\Traits;

use Carbon\Carbon;

trait FilterableByDates
{
    public function scopeToday($query, $column = 'created_at')
    {

akoepcke

module.exports = { 
  // forcing the creation of an index.html for every page to allow
  // providers serving pages without having to add .html to the url
  exportPathMap: async function (defaultPathMap) {
    const pathMap = {};

    for (const [path, config] of Object.entries(defaultPathMap)) {
      if (path === "/") {
        pathMap[path] = config;
      } else {

akoepcke

There are two types of markup in Liquid: Output and Tag.

• Output markup (which may resolve to text) is surrounded by

{{ matched pairs of curly brackets (ie, braces) }}

• Tag markup (which cannot resolve to text) is surrounded by

akoepcke

// Remember to install mini-svg-data-uri
// Follow me on twitter for memes @jordienr

import { type Config } from "tailwindcss";
const {
  default: flattenColorPalette,
} = require("tailwindcss/lib/util/flattenColorPalette");
const svgToDataUri = require("mini-svg-data-uri");

export default {

akoepcke

<?php

use Valet\Drivers\ValetDriver;

class LocalValetDriver extends ValetDriver
{
    public function serves(string $sitePath, string $siteName, string $uri): bool
    {
        return true;
    }

akoepcke

This document provides a comprehensive guide to implementing geospatial queries in Laravel applications. It covers setting up your database, installing necessary packages, defining spatial data in your models, and performing various types of geospatial queries using Laravel's Eloquent ORM and query builder.

Table of Contents:

1. Introduction to Geospatial Queries in Laravel
2. Prerequisites
3. Step 1: Setting up Your Database for Spatial Support
   • 3.1. PostgreSQL with PostGIS Extension (Recommended)
   • 3.2. MySQL (5.6+)
4. Step 2: Configuring Laravel Database Connection

akoepcke

<script setup lang="ts">
import StreamingIndicator from '@/components/StreamingIndicator.vue';
import { useStream } from '@laravel/stream-vue';
import { onMounted, onUnmounted, ref, watch } from 'vue';
type Message = {
    type: 'response' | 'error' | 'prompt';
    content: string;
};
const messages = ref<Message[]>([]);
const { data, send, cancel, isStreaming, id } = useStream('chat');

akoepcke

Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions. This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development work without losing context.

Before providing your final summary, wrap your analysis in <analysis> tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:

1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:
   • The user's explicit requests and intents
   • Your approach to addressing the user's requests
   • Key decisions, technical concepts and code patterns

• Specific details like:

akoepcke

Estimation

This document is an attempt to pin down all the things you don't think about when quoting for a project, and hopefully provide a starting point for some kind of framework to make quoting, working and delivering small-medium jobs more predictable and less stressful.

Contents

• Quoting
• Dependencies
• Skills
• Preparation

akoepcke

#!/bin/bash

LOGFILE="/tmp/git-post-commit.log"
cd "$(git rev-parse --show-toplevel)" || exit 1

# Detect PHP binary in priority order: Herd → Homebrew → system php
if [ -x "/Users/$USER/Library/Application Support/Herd/bin/php" ]; then
  PHP_BIN="/Users/$USER/Library/Application Support/Herd/bin/php"
elif command -v php >/dev/null 2>&1; then
  PHP_BIN="$(command -v php)"