Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Sep 11, 2025

  • Rename compose_pgsql17 service to compose-pgsql17 in docker-compose.yml
  • Update environment configuration
  • Add pghero and grafana services
  • Update GitHub CI workflow to use hyphenated service name (compose-pgsql17)
    • Update docker compose exec commands in neurosynth_compose_backend_tests job
    • Update docker compose exec commands in neurosynth_compose_JUNIT_tests job
    • Update docker compose exec commands in neurosynth_compose_cypress_tests job
    • Update Docker Bake target references from compose_pgsql17. to compose-pgsql17.
  • Add nginx proxy configuration for pghero and grafana services
    • Added /pghero/ location block to nginx.conf and nginx.dev.conf
    • Added /grafana/ location block with rewrite rule to nginx.conf and nginx.dev.conf
    • Configuration matches store project's nginx setup
  • Validate changes are correct

Usage

After applying these changes, users can access monitoring services through nginx:

  1. Access pghero at http://localhost:81/pghero (development) or http://localhost/pghero (production with nginx-proxy)
  2. Access grafana at http://localhost:81/grafana (development) or http://localhost/grafana (production with nginx-proxy)
  3. Login to grafana with credentials: admin/changeme
  4. View pre-configured PostgreSQL datasource for the compose database

This brings the neurosynth-compose project to feature parity with the store project's monitoring capabilities, providing essential observability tools for database performance and system metrics accessible through the nginx reverse proxy.


💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

@jdkent
Copy link
Member

jdkent commented Sep 11, 2025

@copilot the compose_pgsql17 service needs to be renamed to compose-pgsql17 to work with pghero

…afana

Co-authored-by: jdkent <12564882+jdkent@users.noreply.github.com>
Copilot AI changed the title [WIP] add pghero and grafana to neurosynth-compose Add pghero and grafana monitoring services to neurosynth-compose Sep 11, 2025
Copilot AI requested a review from jdkent September 11, 2025 05:41
…ility

Co-authored-by: jdkent <12564882+jdkent@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Sep 11, 2025

@copilot the compose_pgsql17 service needs to be renamed to compose-pgsql17 to work with pghero

Fixed! Renamed the service from compose_pgsql17 to compose-pgsql17 in all necessary locations including the service definition, dependencies, DATABASE_URL, and environment configuration. This change ensures compatibility with pghero. (bd44787)

@jdkent jdkent added this to Planning Dec 19, 2025
@jdkent jdkent moved this to In review in Planning Dec 19, 2025
@jdkent
Copy link
Member

jdkent commented Jan 6, 2026

@copilot please check the builds for github ci and update the names of the containers being built by the ci architecture.

Co-authored-by: jdkent <12564882+jdkent@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Jan 6, 2026

@copilot please check the builds for github ci and update the names of the containers being built by the ci architecture.

Updated all CI workflow references from compose_pgsql17 to compose-pgsql17 in the docker compose exec commands. This includes:

  • neurosynth_compose_backend_tests job (line 260)
  • neurosynth_compose_JUNIT_tests job (line 351)
  • neurosynth_compose_cypress_tests job (line 460)

The changes ensure the CI workflows use the correct hyphenated service name that matches the docker-compose.yml configuration. (4374ecb)

@jdkent
Copy link
Member

jdkent commented Jan 6, 2026

@copilot, in addition the tags need to be updated, like this one: compose_pgsql17.cache-from=type=gha,scope=cached-compose-pgsql17 -> compose-pgsql17.cache-from=type=gha,scope=cached-compose-pgsql17

Co-authored-by: jdkent <12564882+jdkent@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Jan 6, 2026

@copilot, in addition the tags need to be updated, like this one: compose_pgsql17.cache-from=type=gha,scope=cached-compose-pgsql17 -> `compose-pgsql17.cache-from=type=gha,scope=cached-compose-pgsql1...

Updated all Docker Bake target references from compose_pgsql17. to compose-pgsql17. throughout the workflow file. This includes:

  • Build job tags and cache configuration (lines 80-83)
  • neurosynth_compose_backend_tests cache loading (line 245)
  • neurosynth_compose_JUNIT_tests cache loading (line 336)
  • neurosynth_compose_cypress_tests cache loading (line 419)

The target names now match the hyphenated service name defined in docker-compose.yml. (ebe474c)

@jdkent
Copy link
Member

jdkent commented Jan 6, 2026

@copilot, please rebase off of master and see how nginx is setup for neurostore to allow for the services and implement the feature here.

Co-authored-by: jdkent <12564882+jdkent@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Jan 6, 2026

@copilot, please rebase off of master and see how nginx is setup for neurostore to allow for the services and implement the feature here.

Rebased successfully and implemented nginx proxy routes for pghero and grafana services, matching the store setup:

Added to both nginx.conf and nginx.dev.conf:

  • /pghero/ location block proxying to http://pghero:8080/pghero/
  • /grafana/ location block with rewrite rule proxying to http://grafana:3030/

The configuration is identical to the store nginx setup, enabling access to:

  • pghero: http://localhost:81/pghero (or port 80 in production)
  • grafana: http://localhost:81/grafana (or port 80 in production)

All monitoring services are now accessible through the nginx reverse proxy. (8c5c5d3)

@jdkent jdkent marked this pull request as ready for review January 6, 2026 15:11
@jdkent jdkent merged commit a23b365 into master Jan 6, 2026
18 checks passed
@jdkent jdkent deleted the copilot/fix-1135 branch January 6, 2026 15:12
@github-project-automation github-project-automation bot moved this from In review to Done in Planning Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants