AI-Cognitive-Leap/agnes-the-ai-analyst
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
agnes-the-ai-analyst/scripts
History
Petr 86edd27655 Extract Jira into connectors/jira module 
Move all Jira-specific code into a self-contained connector module:
- 22 files moved via git mv (transform, service, webhook, scripts,
  systemd units, tests, docs, bin helper)
- All imports updated to use connectors.jira.* paths
- Jira is now conditional: auto-detected via JIRA_DOMAIN env var
- Webapp registers Jira blueprint only when available
- Health service monitors Jira timers only when enabled
- Profiler loads Jira tables dynamically from filesystem
- Sync settings uses config-driven dependency validation
- Renamed keboola_platform_url -> custom_url in transform
- Updated deploy.sh, sudoers-deploy, backfill_gap.sh paths
- Fixed pytest.ini to skip live tests by default
2026-03-09 11:17:50 +01:00
..
activate_venv.sh Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
backfill_gap.sh Extract Jira into connectors/jira module 2026-03-09 11:17:50 +01:00
collect_session.py Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
duckdb_manager.py Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
generate_user_sync_configs.py Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
init.sh Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
README.md OSS cleanup: remove internal references, harden deployment, add config env interpolation 2026-03-09 07:59:57 +01:00
setup_views.sh Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
sync_config_template.yaml Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
sync_data.sh Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00
update.sh Initial commit: OSS data distribution platform 2026-03-08 23:31:28 +01:00

README.md

Scripts

Helper scripts for working with AI Data Analyst project.

These scripts are synced from the server into server/scripts/ on the analyst's machine.

Available Scripts

setup_views.sh

Initialize or refresh DuckDB views on Parquet files.

bash server/scripts/setup_views.sh

sync_data.sh

Synchronize data from server, upload user files, and refresh DuckDB.

# Recommended: update scripts first, then sync
rsync -avz data-analyst:server/scripts/ ./server/scripts/   # Linux/macOS
scp -r data-analyst:server/scripts/* ./server/scripts/      # Windows fallback
bash server/scripts/sync_data.sh

# Other options:
bash server/scripts/sync_data.sh --dry-run  # Preview what would be synced (no changes)
bash server/scripts/sync_data.sh --push     # Only upload user/ to server

What sync does:

  1. Self-update check - detects if sync_data.sh changed, asks to re-run if so
  2. Downloads server/docs/, server/scripts/, server/metadata/ from server
  3. Updates CLAUDE.md from latest template
  4. Downloads server/parquet/ data files (with --delete to remove old files)
  5. Uploads user/ directory to server (backup, no --delete)
  6. Syncs Python environment to server
  7. Validates DuckDB - if corrupted, deletes and recreates from parquets
  8. Reinitializes DuckDB views (CREATE OR REPLACE VIEW for all tables)

Self-update mechanism: The script checks its own checksum before and after syncing scripts. If it detects it was updated, it exits with a message asking you to run sync again. This ensures you always run the latest sync logic.

DuckDB corruption recovery: If DuckDB file is corrupted (e.g., interrupted sync), it's automatically detected and recreated. All data is safe in parquet files - DuckDB only contains VIEW definitions.

Typical Workflow

  1. First time setup: Follow bootstrap.yaml instructions
  2. Before analysis: Sync latest data 
    bash server/scripts/sync_data.sh
  3. Analyze: Use DuckDB database at user/duckdb/analytics.duckdb