The only tool you need to know what is happening and how to fix it.
Go alertingexception-trackerissue-trackinglogsmetricsmonitoringobservability-platformopen-telemetryotelsession-replaytelemetrytraces
sqlite docs fixed
ddux3673b48a7771
diff --git a/docs/pages/server/sqlite.mdx b/docs/pages/server/sqlite.mdxindex 5f4c82be..5eb2b5d9 100644--- a/docs/pages/server/sqlite.mdx+++ b/docs/pages/server/sqlite.mdx@@ -116,7 +116,11 @@ docker stop traceway && docker rm traceway**2. Point Railway at `Dockerfile.sqlite`.** Open **Settings → Build** on the service and set **Custom Dockerfile Path** to `Dockerfile.sqlite`. Railway will use that Dockerfile for every deploy.-**3. Add a volume at `/data`.** Open **Settings → Volumes**, add a new volume, and set the mount path to `/data`. Without this, your SQLite files and uploaded blobs get wiped on every redeploy.+**3. Attach a volume at `/data`.** Right-click the service tile and pick **Attach volume**, then enter `/data` as the mount path. Without this, your SQLite files and uploaded blobs get wiped on every redeploy.++<img src="/railway-attach-volume.png" alt="Railway service context menu with Attach volume highlighted" style={{ maxWidth: 280, height: 'auto', display: 'block', marginTop: '0.75rem' }} />++<img src="/railway-volume-mount-path.png" alt="Railway volume mount path field set to /data" style={{ maxWidth: 320, height: 'auto', display: 'block', marginTop: '0.75rem' }} />**4. Set environment variables.** Open **Variables** and add:diff --git a/docs/public/railway-attach-volume.png b/docs/public/railway-attach-volume.pngnew file mode 100644index 00000000..185fc789Binary files /dev/null and b/docs/public/railway-attach-volume.png differdiff --git a/docs/public/railway-volume-mount-path.png b/docs/public/railway-volume-mount-path.pngnew file mode 100644index 00000000..088bb1a9Binary files /dev/null and b/docs/public/railway-volume-mount-path.png differ