Skip to content

Commit f6f311c

Browse files
committed
fix compile flag and use single port
1 parent 0dc82e2 commit f6f311c

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

  • skills/reflex-process-management

skills/reflex-process-management/SKILL.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
name: reflex-process-management
33
description: >
44
Manage Reflex application processes: compile to test, run the server in production mode,
5-
reload a running app by finding and restarting the backend process, and manage logs for
5+
reload a running app by finding and restarting the app process, and manage logs for
66
debugging. Use when the user wants to test, run, restart, or reload a Reflex app,
77
when troubleshooting a running Reflex server, or when investigating errors.
88
---
@@ -16,7 +16,7 @@ This skill covers how to compile, run, and reload a Reflex application.
1616
To verify the app compiles without errors, run:
1717

1818
```bash
19-
reflex compile --dry-run
19+
reflex compile --dry
2020
```
2121

2222
This checks for syntax errors, import issues, and component problems without starting the server. Use this as a quick validation step after making changes.
@@ -26,7 +26,7 @@ This checks for syntax errors, import issues, and component problems without sta
2626
When instructed to run the Reflex server, always use production mode and redirect output to a log file:
2727

2828
```bash
29-
reflex run --env prod 2>&1 | tee reflex.log
29+
reflex run --env prod --single-port 2>&1 | tee reflex.log
3030
```
3131

3232
This command starts a long-running server process that **does not support hot reload** in production mode. Code changes will not be picked up automatically — you must stop and restart the server to apply changes (see **Reloading a Running App** below).
@@ -39,11 +39,11 @@ Using `2>&1 | tee reflex.log` captures both stdout and stderr to `reflex.log` wh
3939

4040
To reload the app without manually stopping and restarting from the terminal, follow these steps:
4141

42-
### Step 1: Determine the backend port
42+
### Step 1: Determine the app port
4343

44-
Read `reflex.log` to find the port the backend is listening on. Look for a line like `Backend running at: http://0.0.0.0:<port>`. Do not assume the port is 8000.
44+
Read `reflex.log` to find the port the app is listening on. Look for a line like `App running at: http://0.0.0.0:<port>`. Do not assume the port is 8000.
4545

46-
### Step 2: Find the backend process
46+
### Step 2: Find the app process
4747

4848
Using the port from Step 1, locate the process:
4949

@@ -83,7 +83,7 @@ Once the old process has exited, truncate the old log and start the server again
8383

8484
```bash
8585
> reflex.log
86-
reflex run --env prod 2>&1 | tee reflex.log
86+
reflex run --env prod --single-port 2>&1 | tee reflex.log
8787
```
8888

8989
## Investigating Errors

0 commit comments

Comments
 (0)