fix/ remove container name from docker compose

This commit is contained in:
Leon van Zyl
2025-11-06 07:17:58 +02:00
parent 61e98f23cf
commit bd74276feb
6 changed files with 35 additions and 12 deletions

View File

@@ -1,6 +1,6 @@
{ {
"name": "create-agentic-app", "name": "create-agentic-app",
"version": "1.0.1", "version": "1.0.2",
"description": "Scaffold a new agentic AI application with Next.js, Better Auth, and AI SDK", "description": "Scaffold a new agentic AI application with Next.js, Better Auth, and AI SDK",
"type": "module", "type": "module",
"bin": { "bin": {

View File

@@ -1,2 +1,32 @@
Please commit all changes and provide a suitable comment for the commit. Please create a comprehensive checkpoint commit with the following steps:
Run git init if git has not been instantiated for the project as yet.
1. **Initialize Git if needed**: Run `git init` if git has not been instantiated for the project yet.
2. **Analyze all changes**:
- Run `git status` to see all tracked and untracked files
- Run `git diff` to see detailed changes in tracked files
- Run `git log -5 --oneline` to understand the commit message style of this repository
3. **Stage everything**:
- Add ALL tracked changes (modified and deleted files)
- Add ALL untracked files (new files)
- Use `git add -A` or `git add .` to stage everything
4. **Create a detailed commit message**:
- **First line**: Write a clear, concise summary (50-72 chars) describing the primary change
- Use imperative mood (e.g., "Add feature" not "Added feature")
- Examples: "feat: add user authentication", "fix: resolve database connection issue", "refactor: improve API route structure"
- **Body**: Provide a detailed description including:
- What changes were made (list of key modifications)
- Why these changes were made (purpose/motivation)
- Any important technical details or decisions
- Breaking changes or migration notes if applicable
- **Footer**: Include co-author attribution as shown in the Git Safety Protocol
5. **Execute the commit**: Create the commit with the properly formatted message following this repository's conventions.
IMPORTANT:
- Do NOT skip any files - include everything
- Make the commit message descriptive enough that someone reviewing the git log can understand what was accomplished
- Follow the project's existing commit message conventions (check git log first)
- Include the Claude Code co-author attribution in the commit message

View File

@@ -1,9 +1,6 @@
version: "3.8"
services: services:
postgres: postgres:
image: pgvector/pgvector:pg18 image: pgvector/pgvector:pg18
container_name: postgres
environment: environment:
POSTGRES_DB: postgres_dev POSTGRES_DB: postgres_dev
POSTGRES_USER: dev_user POSTGRES_USER: dev_user

View File

@@ -1,6 +1,6 @@
{ {
"name": "agentic-coding-starter-kit", "name": "agentic-coding-starter-kit",
"version": "0.1.1", "version": "1.1.2",
"scripts": { "scripts": {
"dev": "next dev --turbopack", "dev": "next dev --turbopack",
"build": "pnpm run db:migrate && next build", "build": "pnpm run db:migrate && next build",

View File

@@ -1,9 +1,6 @@
version: "3.8"
services: services:
postgres: postgres:
image: pgvector/pgvector:pg18 image: pgvector/pgvector:pg18
container_name: postgres
environment: environment:
POSTGRES_DB: postgres_dev POSTGRES_DB: postgres_dev
POSTGRES_USER: dev_user POSTGRES_USER: dev_user

View File

@@ -1,7 +1,6 @@
{ {
"name": "agentic-coding-starter-kit", "name": "agentic-coding-starter-kit",
"version": "0.1.1", "version": "1.1.2",
"private": true,
"scripts": { "scripts": {
"dev": "next dev --turbopack", "dev": "next dev --turbopack",
"build": "pnpm run db:migrate && next build", "build": "pnpm run db:migrate && next build",