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
We've had a few external folks setting up ohmage servers who have used this package, but are very confused about the web frontend's endpoint. since it's hosted at /ohmage by default on your installs, it appears that all of the ohmage code is housed there, instead of it just being the frontend code.
I understand that you were quite against using /web for the frontend, since it was generic, (although, /app is generic) but can we modify the web front-end endpoint to at least make troubleshooting a bit easier? something like /gwt if you don't want to use /web (we use /web internally, which I think would be great).
thanks!
The text was updated successfully, but these errors were encountered:
We've had a few external folks setting up ohmage servers who have used this package, but are very confused about the web frontend's endpoint. since it's hosted at /ohmage by default on your installs, it appears that all of the ohmage code is housed there, instead of it just being the frontend code.
I understand that you were quite against using /web for the frontend, since it was generic, (although, /app is generic) but can we modify the web front-end endpoint to at least make troubleshooting a bit easier? something like /gwt if you don't want to use /web (we use /web internally, which I think would be great).
thanks!
The text was updated successfully, but these errors were encountered: