NER Team

[ryanwesslen]

hi @kushalrsharma!

@kushalrsharma

do this works in case of different users connected to the same wifi?

I think the answer is yes. I'm a bit confused on what you mean by "connected to the same wifi". Typically, they need access to the server that hosts your Prodigy session and that host was modified (e.g., 0.0.0.0).

Serving on other than localhost

Hi! I’d like to run the annotation UI on our local server and access it without ssh tunneling. For this it would be nice if I can set the serving ip other than “localhost” (e.g “0.0.0.0”). I could not find nor a "host" nor an "ip" option in the readme, but luckily this just worked fine: {"host": "0.0.0.0"} I’d suggest to document this in the readme. /Gyuri

User authentication for Prodigy web app

Setting the host to “0.0.0.0” (any IP on the machine) solved it! Thanks a lot, @honnibal

But please remember -- there are many challenges in setting up annotators to access from external computers like firewall, reverse proxy for setting up https, authentication, etc. Here are just a few examples:

Access Prodigy from external computer

Dear All, Really happy with Prodigy. Until now, due to our requirements, we had all annotators annotate locally. However now we try to setup a server such that multiple annotators can code on one instance. We setup prodigy on Ubuntu 20.04, no other webservices are running. A) python3 -m prodigy ner.manual etc…………. We can access prodigy on localhost:8080 We can access prodigy on 127.0.0.1:8080 We are not able to reach Prodigy from an external computer. We added rules to the firewall: …

Prodigy with https

I would recommend adding a reverse proxy in front that is restricted to only https connections. For instance, you would advertise the service on localhost, and have something like Nginx, Traefik or Apache communicating externally, via https.

authentication out of the box

You can set up the basic auth using the environment variables PRODIGY_BASIC_AUTH_USER and PRODIGY_BASIC_AUTH_PASS. See here for an example: If you want a fully custom solution, you could also add you own authentication miniservice that asks the user to log in and then starts up the server and redirects them. You can find different approaches for this on the forum.

My main takeaway is please remember to keep searching for past tickets. While we'll do our best to help, this is a non-trivial problem to scale up many annotators. We have found many users can create such processes on their own, but they need to have good skills in managing networks/security and it takes time to develop these.