fix: attempt to get staging env running again

Author: johnbchron

.github/workflows/deploy.yml

@@ -13,6 +13,6 @@ jobs:
       - uses: actions/checkout@v4
       - uses: DeterminateSystems/nix-installer-action@main
       - uses: superfly/flyctl-actions/setup-flyctl@master
-      - run:  docker load -i $(nix build ".#grid-container" -L --no-link --print-out-paths) && flyctl deploy --local-only --detach
+      - run:  docker load -i $(nix build ".#grid-container" -L --no-link --print-out-paths) && flyctl deploy -c fly/app.toml --local-only --detach
         env:
           FLY_API_TOKEN: ${{ secrets.FLY_DEPLOY_TOKEN }}

fly.toml fly/app.tomlfly.toml renamed to fly/app.toml

@@ -13,5 +13,9 @@ min_machines_running = 0
 # axum is http2-enabled
 http_options.h2_backend = true
 
+[env]
+GRID_ENV = "staging"
+RUST_LOG = "info,grid=debug,domain=debug,tower_http=debug"
+
 [[vm]]
 size = 'shared-cpu-1x'

fly/quickwit.toml

@@ -0,0 +1,35 @@
+# fly.toml app configuration file generated for quickwit-misty-moon-5123 on 2025-12-01T21:20:45-08:00
+#
+# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
+#
+
+app = 'quickwit-misty-moon-5123'
+primary_region = 'iad'
+
+[build]
+image = 'quickwit/quickwit:latest'
+
+[experimental]
+cmd = [ "run" ]
+
+[env]
+# Required secrets:
+# - AWS_ACCESS_KEY_ID (R2 access key)
+# - AWS_SECRET_ACCESS_KEY (R2 secret key)
+# - AWS_ENDPOINT_URL (R2 endpoint)
+AWS_REGION = 'auto'
+QW_CLUSTER_ID = 'quickwit-cluster'
+QW_DATA_DIR = '/quickwit/qwdata'
+QW_DEFAULT_INDEX_ROOT_URI = 's3://rambit-quickwit/indexes'
+QW_LISTEN_ADDRESS = '::'
+QW_NODE_ID = 'node-1'
+
+[[mounts]]
+destination = '/quickwit/qwdata'
+initial_size = '10gb'
+source = 'quickwit_data'
+
+[[vm]]
+cpu_kind = 'shared'
+cpus = 2
+memory = '2gb'