fix makefile to not accidentally rebuild-expensive-builds

Author: martyall

.tmuxinator.yml

@@ -6,8 +6,6 @@ on_project_start:
   - sleep 5
   - make create-db
   - make create-schema
-  - make build-prover
-  - make build-monitor
 
 windows:
   - eth_pg_logs:
@@ -27,7 +25,6 @@ windows:
           NODE_HOST=localhost
           NODE_PORT=8545
           JSON_RPC_PORT=3000
-          RISC0_DEV_MODE=true
           RUST_LOG=debug
           make run-prover-server
         - >

Makefile

@@ -168,7 +168,7 @@ run-prover-server: ## Run the prover server
 	JSON_RPC_PORT=$(PROVER_PORT) \
 	RISC0_DEV_MODE=${RISC0_DEV_MODE} \
 	IMAGE_ID_CONTRACT=$(IMAGE_ID_CONTRACT) \
-	cargo run -p monitor-server --bin prover-server -F local_prover $(CARGO_BUILD_OPTIONS)
+	./target/release/prover-server
 
 run-monitor-server: build-monitor ## Run the monitor server
 	DB_HOST=$(DB_HOST) \
@@ -182,7 +182,7 @@ run-monitor-server: build-monitor ## Run the monitor server
 	PROVER_HOST=$(PROVER_HOST) \
 	PROVER_PORT=$(PROVER_PORT) \
 	JSON_RPC_PORT=$(MONITOR_PORT) \
-	cargo run -p monitor-server --bin monitor-server $(CARGO_BUILD_OPTIONS)
+	./target/release/monitor-server
 
 fetch-image-id-contract: ## Fetch the ImageID contract from the monitor server
 	@curl -f -s -XPOST -H "Content-Type: application/json" \

README.md

@@ -25,13 +25,17 @@ Two tmuxinator configurations are provided for development. Both configurations
 #### 1. Local Development (`.tmuxinator.yml`)
 Run services locally with cargo:
 ```bash
-tmuxinator start -p .tmuxinator.yml
+make build-monitor
+make build-prover # Or make make build-prover-cuda for gpu
+RISC0_DEV_MODE={true/false} tmuxinator start -p .tmuxinator.yml
 ```
 
 #### 2. Docker Development (`.tmuxinator.docker.yml`)
+make build-monitor
+make build-prover # Or make make build-prover-cuda for gpu
 Run all services in Docker containers:
 ```bash
-tmuxinator start -p .tmuxinator.docker.yml
+RISC0_DEV_MODE={true/false} tmuxinator start -p .tmuxinator.docker.yml
 ```
 
 ## Testing
@@ -61,4 +65,4 @@ You should see the deploy address of the TTC contract printed to the console. Th
 ```
 
 You can control the log level via `RUST_LOG`. This script creates checkpoints, writing the relevant state to `./deployments/<ttc-contract-address>`. If the script errors or halts at any
-time, you can re-run from the last checkpoint using the same command as you used to start.
+time, you can re-run from the last checkpoint using the same command as you used to start.