A lightweight, multi-tenant, scalable and secure gateway that enables Jupyter Notebooks to share resources across distributed clusters such as Apache Spark, Kubernetes and others.
The EG "website" was meant to be posted at jupyter.org/enterprise-gateway but that produces a 404. The website consists of essentially two files - one briefly describing the Kubernetes deployment, and the other describes a Spark YARN cluster. Both pages then reference ansible deployment scripts from a personal repo that are minimally maintained (and unnecessary for Kubernetes since Helm is the de-facto way to deploy). Our documentation provides similar, more detailed, and current, information.
I think we should first decide if the website is necessary. I believe its initial purpose was to get an idea of how many "visits" it received via google analytics since, at the time, we were a fledgling project. Is this necessary and worth the maintenance burden since it's essentially redundant information?
Should we decide a separate website is necessary (beyond the GitHub repo and readthedocs pages), we need to figure out where it will be exposed and hosted.
The EG "website" was meant to be posted at
jupyter.org/enterprise-gatewaybut that produces a 404. The website consists of essentially two files - one briefly describing the Kubernetes deployment, and the other describes a Spark YARN cluster. Both pages then reference ansible deployment scripts from a personal repo that are minimally maintained (and unnecessary for Kubernetes since Helm is the de-facto way to deploy). Our documentation provides similar, more detailed, and current, information.I think we should first decide if the website is necessary. I believe its initial purpose was to get an idea of how many "visits" it received via google analytics since, at the time, we were a fledgling project. Is this necessary and worth the maintenance burden since it's essentially redundant information?
Should we decide a separate website is necessary (beyond the GitHub repo and readthedocs pages), we need to figure out where it will be exposed and hosted.