Maintenance

Once Isekai Core is running, you’ll need to perform occasional maintenance tasks.

Updating Isekai Core

We release updates frequently with new features and bug fixes. Updating your Docker-based installation is simple.

Docker Compose (VPS)

1. Pull the latest images

   docker compose pull

2. Recreate containers (this minimizes downtime)

   docker compose up -d

3. Prune old images (optional, saves disk space)

   docker image prune -f

Coolify / Dokploy

1. Go to your resource dashboard.

2. Click the Redeploy or Force Rebuild button.

3. The system will automatically pull the latest tag and restart the containers.

Database Migrations

Note

In most cases, the application will automatically run necessary database migrations when the new container starts. If you encounter database errors after an update, check the container logs.

Backups

Your data lives in two places:

• PostgreSQL Database: Contains all user data, draft text, schedules, and automation rules.
• S3 Storage: Contains the actual image files (MinIO, Cloudflare R2, AWS S3, etc.).

What to Backup

You primarily need to backup the PostgreSQL Database and your .env file.

• S3 Storage: If using local MinIO, backup the minio_data Docker volume. Cloud providers (R2, S3) are highly durable.
• Redis: Strictly cache and temporary job queues. No backup needed.

Automated Postgres Backups (Docker)

If you are using the default docker-compose.yml, you can create a cron job to backup the database container:

# Backup script example
docker exec isekai-postgres pg_dump -U isekai isekai > /path/to/backups/isekai_$(date +%F).sql

Restoring Data

To restore a database dump:

1. Stop the app first

   docker stop isekai-backend

2. Restore command

   cat backup.sql | docker exec -i isekai-postgres psql -U isekai