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

Add zipping packages to a default TLJH #121

Closed
choldgraf opened this issue Aug 10, 2018 · 4 comments
Closed

Add zipping packages to a default TLJH #121

choldgraf opened this issue Aug 10, 2018 · 4 comments

Comments

@choldgraf
Copy link
Member

It seems like it may be common for people to want to download zipped and/or compressed files on a JupyterHub. Perhaps we should add packages like unzip by default? What do folks think?

(I know tar is already installed, but lots of datasets are stored as .zip out there)

@yuvipanda
Copy link
Collaborator

This is the general question of 'what additional apt 'utilities' do we add to TLJH'. For right now, my preference is 'none', at least until we have a policy on what gets added and what does not. Primarily I'm concerned about install time, and also around bloat if we don't have a clear policy for what things we 'automatically' install.

In the meantime, maybe make our howto on using apt more prominent?

@choldgraf
Copy link
Member Author

Fine w/ me - I added an example that included installing unzip to download a data file in the latest PR, so I think we can probably doc-around this problem :-)

@yuvipanda
Copy link
Collaborator

@choldgraf The way to do this is to allow people to make 'spins' or 'variants' of TLJH with plugins, in an easy way that puts very little burden on both the people making the spins/variants and the users. The plugin approach in #127 should help with this! We can then have a webpage that constructs an install command based on the plugins they want.

@choldgraf
Copy link
Member Author

that's a cool idea - I like it! I suppose is people start doing this, we can occasionally see whether there is a particular package / pattern that everybody uses in their package and then decide if it makes sense to bake that in to TLJH in subsequent versions.

I'm gonna close this because I think it's too specific to be actionable, but re-open if you disagree!

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

No branches or pull requests

2 participants