gradio/website
2022-01-20 09:53:25 -06:00
..
demos fix static paths and demo launch 2021-12-26 22:30:19 -08:00
homepage chatbot tutorial 2022-01-20 09:53:25 -06:00
upload_notebooks autoreload website on changes 2021-12-16 15:08:27 -08:00
.gitignore Website: WIP (#328) 2021-12-13 22:02:19 -08:00
docker-compose.yml Website: WIP (#328) 2021-12-13 22:02:19 -08:00
gradio.nginx.conf fix gradio web embeds 2021-12-22 08:45:23 +00:00
package-lock.json Website: WIP (#328) 2021-12-13 22:02:19 -08:00
README.md Update README.md 2021-12-16 15:18:48 -08:00
reload_website.sh fix website reloader 2021-12-16 19:41:14 -08:00

The Gradio Website

The Gradio website (https://gradio.app) is built from the contents of this folder. The website is tightly coupled with the rest of the repository through several ways:

  • The gradio library used to run the demos throughout the website is built from the library in the gradio folder of this repository
  • The demos are loaded from the gradio/demo folder
  • The guide pages are loaded from the gradio/guides folder
  • The documentation is loaded from the docstrings in the library itself.

The website is launched through the docker-compose.yml file in this directory.

The homepage docker

The homepage folder builds the static content of the website into standalone files, served by nginx in docker. For development purposes, instead of running docker to test changes, follow these steps in the homepage folder.

  • npm install
  • npm run build (or npm run start for automatic reload on change).

The website will be built in the homepage/dist directory. You can run a development server from this directory to launch the homepage, e.g. python -m http.server. See homepage/package.json for build steps.

The demos docker

The demos folder launches all the demos embedded inside the website. The demos are loaded from the gradio/demo folder.

The upload_notebooks folder

The upload_notebooks folder runs a script that uploads the demos within gradio/demo to Google Colab. The links generated from uploading these files are then stored in the docker env file, which is then used by the homepage docker container to link to the Colab notebooks from the documentation.

Auto-Reloading

The website is built from the master branch and automatically reloads on commits to master.