fix: entrypoint seed check handles empty databases
Check for content entries, not just file existence. If data.db exists but has no content, still run seed to populate. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,10 +1,11 @@
|
||||
#!/bin/sh
|
||||
# Only seed on first launch (when data.db doesn't exist)
|
||||
if [ ! -f data.db ]; then
|
||||
echo "Database missing, running emdash init & seed..."
|
||||
# Only seed on first launch (when data.db doesn't exist or is empty)
|
||||
# Check if content table has any entries
|
||||
if [ ! -f data.db ] || ! sqlite3 data.db "SELECT COUNT(*) FROM content" 2>/dev/null | grep -q "^[1-9]"; then
|
||||
echo "Database missing or empty, running emdash init & seed..."
|
||||
pnpm exec emdash init
|
||||
pnpm exec emdash seed
|
||||
else
|
||||
echo "Database exists, starting normally..."
|
||||
echo "Database exists with content, starting normally..."
|
||||
fi
|
||||
exec node ./dist/server/entry.mjs
|
||||
Reference in New Issue
Block a user