Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out what to do with the EG website #1174

Open
kevin-bates opened this issue Oct 19, 2022 · 0 comments
Open

Figure out what to do with the EG website #1174

kevin-bates opened this issue Oct 19, 2022 · 0 comments
Assignees

Comments

@kevin-bates
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants