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
To make sure a new renderer is functioning properly, it's recommended that you try to render a file of that type locally.
109
110
110
-
First, change the default provider to HTTP (in `/mfr/server/settings.py`) and update the provider domain whitelist:
111
+
First, change the default provider to HTTP (in `/mfr/server/settings.py`), then update the provider domain in the ``ALLOWED_PROVIDER_DOMAINS`` whitelist (a space-separated string):
A Python package for rendering files to HTML via an embeddable iframe.
8
10
9
11
### Compatibility
@@ -53,12 +55,12 @@ MFR configuration is done through a JSON file (`mfr-test.json`) that lives in th
53
55
mkdir ~/.cos
54
56
```
55
57
56
-
The defaults should suffice for most local testing. If you're running the OSF on something other than `http://localhost:5000/`, you'll need to update the `ALLOWED_PROVIDER_DOMAINS` settings value:
58
+
The defaults should suffice for most local testing. If you're running the OSF or WaterButler on something other than `http://localhost:5000/` and `http://localhost:7777/`, you'll need to update the `ALLOWED_PROVIDER_DOMAINS` settings value. `ALLOWED_PROVIDER_DOMAINS` is a list formatted as a space-separated string. This allows MFR to be configured via an environment variable (which are always strings), as is done in the OSF's `.docker-compose.mfr.env`. Example of customized domains:
0 commit comments