You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repo is a part of hubploy in that it is the required directory structure and enables new users to get started much faster by templating their own repos with this one. That said, this repo is very far behind hubploy development and documentation. Here are some thing I'd like to update:
Readme: The readme is the old deployment instructions. These instructions now live in the docs, so we can update the Readme to have a more high-level description with links to hubploy, the docs, etc.
Hubploy image: this uses an old version of hubploy as-is and that version should be updated.
Local install instructions: The first deployment is recommended by command-line, which is fine. However, this has you do a pip install, which I haven't had success with in a while because it links to an old version. It looks like we can just change the commit hash in requirements.txt to be more up-to-date and update it on stable "releases." I've done a lot of local hubploy installing / linking with pip install -e ~/<absolute-path-to>/hubploy but I'm unsure if we should recommend that. It's mentioned in the docs for setting up a dev environment; maybe that's good enough.
This repo is a part of
hubploy
in that it is the required directory structure and enables new users to get started much faster by templating their own repos with this one. That said, this repo is very far behindhubploy
development and documentation. Here are some thing I'd like to update:hubploy
as-is and that version should be updated.pip
install, which I haven't had success with in a while because it links to an old version. It looks like we can just change the commit hash inrequirements.txt
to be more up-to-date and update it on stable "releases." I've done a lot of localhubploy
installing / linking withpip install -e ~/<absolute-path-to>/hubploy
but I'm unsure if we should recommend that. It's mentioned in the docs for setting up a dev environment; maybe that's good enough.default
. See Kubeconfig update call requires default aws credentials berkeley-dsep-infra/hubploy#45Will think more on this. Feel free to suggest more changes on how we can make this repo helpful and easy to use!
The text was updated successfully, but these errors were encountered: