You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,34 @@ This path is designed to work even when:
40
40
- you do not have an OpenAI API key yet
41
41
- you are cloning the repo onto a new machine for the first time
42
42
43
+
## Generate a Private Workspace
44
+
45
+
If you do not want to work directly in this public repository, you can use it as a generator for a new private local project.
46
+
47
+
Example:
48
+
49
+
```bash
50
+
bash scripts/init_private_workspace.sh ~/Projects/my-private-pathology --name "My Private Pathology"
51
+
```
52
+
53
+
That command creates a new workspace folder with:
54
+
55
+
- its own `.env`
56
+
- its own `config/library.local.yaml`
57
+
- a namespaced Docker Compose project name
58
+
- isolated API and PostgreSQL host ports
59
+
- namespaced CLI wrapper names such as `pathology-client-my-private-pathology`
60
+
- an optional fresh git repository
61
+
62
+
Then you switch into the generated folder and deploy it there:
63
+
64
+
```bash
65
+
cd~/Projects/my-private-pathology
66
+
bash scripts/deploy_portable.sh --allow-no-openai
67
+
```
68
+
69
+
This is the closest path to generating a new local project that behaves like the original private `pathology-ai` setup, but without carrying over public git history or shared runtime settings.
70
+
43
71
## Five-Minute Onboarding
44
72
45
73
### 1. Prerequisites
@@ -206,6 +234,7 @@ Direct script entrypoints:
206
234
```bash
207
235
bash scripts/doctor.sh
208
236
bash scripts/bootstrap.sh
237
+
bash scripts/init_private_workspace.sh ~/Projects/my-private-pathology --name "My Private Pathology"
0 commit comments