Field report: Noisy translation data annotation and nginx-proxy deployment

[ines (Ines Montani)]

Thank for sharing

@baeumer

Especially not, because you can't define a text for the user inputs (only a placeholder). For this reason, it is necessary to work with HTML.

I hope I understand the question correctly but you can also pre-populate the text in the text field in the incoming JSON. By default, that'd be user_input, but you can also customise the ID via the field_id setting on the block. So if you feed in data with "user_inpit": "Some text here", the field will get pre-populated.

@baeumer

If a reverse proxy is to be used with nginx and the paths cannot be "/" because, for example, something else is already running on the path, as far as I know you have no way in Prodigy to define an alternative route here.

Couldn't you do something like this and define alternative routes for all the endpoints?

Using Prodigy with a ProxyPass

@elly Thanks Ellen, that worked for me too! In case someone else stumbles upon this thread looking for a solution for Nginx, it’s straight forward based on Ellen’s post: location /annotate/ { proxy_pass http://localhost:8080/; } location /project { proxy_pass http://localhost:8080/project; } location /get_questions { proxy_pass http://localhost:8080/get_questions; } location /give_answers { proxy_pass http://localhost:8080/give_answers; } location /fonts { proxy_pass http:/…

In general, Prodigy should support custom path-based routing because all requests are made using the releative paths.