Spaces:
Running
Running
Commit
·
14ba40f
1
Parent(s):
194112d
clarify why/when not to use dev mode
Browse files
README.md
CHANGED
@@ -133,7 +133,11 @@ That said, please see the "RUN" section for info about environement variables.
|
|
133 |
|
134 |
### Dev mode on Hugging Face
|
135 |
|
136 |
-
|
|
|
|
|
|
|
|
|
137 |
|
138 |
```
|
139 |
pip install -r requirements.txt
|
@@ -141,6 +145,8 @@ pip install -r requirements.txt
|
|
141 |
|
142 |
As this is not automatic, then click on "Restart" in the space dev mode UI widget.
|
143 |
|
|
|
|
|
144 |
### Full installation somewhere else
|
145 |
|
146 |
I haven't tested it, but you can try to provided Dockerfile
|
|
|
133 |
|
134 |
### Dev mode on Hugging Face
|
135 |
|
136 |
+
I recommend to not use the dev mode for a production usage (ie not use dev mode when training a real model), unless you know what you are doing.
|
137 |
+
|
138 |
+
That's because the dev mode can be unstable and cause space restarts.
|
139 |
+
|
140 |
+
If you still want to open the dev mode in the space, then open VSCode in local or remote and run:
|
141 |
|
142 |
```
|
143 |
pip install -r requirements.txt
|
|
|
145 |
|
146 |
As this is not automatic, then click on "Restart" in the space dev mode UI widget.
|
147 |
|
148 |
+
Important: if you see errors like "API not found" etc, it might indicate an issue with the dev mode and Gradio, not an issue with VMS itself.
|
149 |
+
|
150 |
### Full installation somewhere else
|
151 |
|
152 |
I haven't tested it, but you can try to provided Dockerfile
|