Everyvoice demo needs a "--port " or -p swich ELSE default is 7860

[marctessier]

Description & Motivation

When we start the demo with everyvoice, the default listening port is 7860.

(EveryVoice) [U20-GPSC5]:$ everyvoice demo  ./logs_and_checkpoints/FeaturePredictionExperiment/base/checkpoints/last.ckpt ../../MODELS/hifigan_universal_v1_everyvoice.ckpt
⠹ Loading... (0:01:27.46)/gpfs/fs5/nrc/nrc-fs1/ict/others/u/tes001/miniforge3/envs/EveryVoice/lib/python3.10/site-packages/torch/cuda/__init__.py:611: UserWarning: Can't initialize NVML
  warnings.warn("Can't initialize NVML")
Done Loading... (0:01:41.05)
* Running on local URL:  http://127.0.0.1:7860
INFO - HTTP Request: GET http://127.0.0.1:7860/gradio_api/startup-events "HTTP/1.1 200 OK"
INFO - HTTP Request: HEAD http://127.0.0.1:7860/ "HTTP/1.1 200 OK"

Currently, what I am doing is exporting variable GRADIO_SERVER_PORT with the port that I define.

ex using port 6004:

(EveryVoice) [U20-GPSC5]:$ export GRADIO_SERVER_PORT=6004
(EveryVoice) [U20-GPSC5]:$ everyvoice demo  ./logs_and_checkpoints/FeaturePredictionExperiment/base/checkpoints/last.ckpt ../../MODELS/hifigan_universal_v1_everyvoice.ckpt
⠦ Loading... (0:00:20.85)/gpfs/fs5/nrc/nrc-fs1/ict/others/u/tes001/miniforge3/envs/EveryVoice/lib/python3.10/site-packages/torch/cuda/__init__.py:611: UserWarning: Can't initialize NVML
  warnings.warn("Can't initialize NVML")
Done Loading... (0:00:27.92)
* Running on local URL:  http://127.0.0.1:6004
INFO - HTTP Request: GET http://127.0.0.1:6004/gradio_api/startup-events "HTTP/1.1 200 OK"
INFO - HTTP Request: GET https://api.gradio.app/pkg-version "HTTP/1.1 200 OK"
INFO - HTTP Request: HEAD http://127.0.0.1:6004/ "HTTP/1.1 200 OK"

To create a public link, set `share=True` in `launch()`

Pitch

Give more flexibility to the end users. Make's it easier to use the demo / pre-define your port forwards...

Alternatives

Could just add some extra documentation to tell the end users to export the variable " GRADIO_SERVER_PORT" BUT I think having the switch made available would be the proper thing to do.

Additional context

No response