Skip to content

Commit f7e7955

Browse files
authored
Update README.md
1 parent b0f997a commit f7e7955

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ dataset = await artifact_manager.create(
176176
# Access the artifact through elFinder
177177
async def setup():
178178
fm = await api.showDialog(
179-
src="http://localhost:3000"
179+
src="https://fm.imjoy.io"
180180
)
181181
await fm.mount("https://hypha.aicell.io/workspace/example-dataset", {"token": token})
182182

@@ -185,12 +185,12 @@ api.export({"setup": setup})
185185

186186
You can also access artifacts directly through the elFinder URL:
187187
```
188-
http://localhost:3000/?mount=https://hypha.aicell.io/workspace/artifact-alias
188+
https://fm.imjoy.io/?mount=https://hypha.aicell.io/workspace/artifact-alias
189189
```
190190

191191
For private artifacts that require authentication, append a token:
192192
```
193-
http://localhost:3000/?mount=https://hypha.aicell.io/workspace/artifact-alias&token=your-token
193+
https://fm.imjoy.io/?mount=https://hypha.aicell.io/workspace/artifact-alias&token=your-token
194194
```
195195

196196
#### Using elFinder with Artifact Manager in ImJoy
@@ -243,7 +243,7 @@ api.export({"setup": setup})
243243
elFinder uses a service worker for managing file operations and caching. Sometimes you may need to force the service worker to upgrade, especially after updates to the elFinder codebase. You can force an upgrade by adding the `upgrade=1` parameter to the URL:
244244

245245
```
246-
http://localhost:3000/?mount=https://hypha.aicell.io/workspace/artifact-alias&upgrade=1
246+
https://fm.imjoy.io/?mount=https://hypha.aicell.io/workspace/artifact-alias&upgrade=1
247247
```
248248

249249
**Note:** After adding the upgrade parameter, you may need to refresh the page a few times in your browser for the upgrade to take effect. This is because service worker updates follow a specific lifecycle and may require multiple refreshes to fully activate.

0 commit comments

Comments
 (0)