Recent blog posts

2i2c are pleased to announce the development and deployment of automated backups of home directories on GCP-hosted hubs! We have developed the gcp-filestore-backups project that regularly creates backups of JupyterHub home directories for disaster recovery purposes.

This quarterly post is coming out a little bit late - our goal was to post this in early January, but the year has been more complicated than we bargained for :-)

If you’re interested in supporting mybinder.org with cloud resources, financial resources, or human resources, please see the Support Binder page for how you can help. tl;dr: The 2i2c team is joining the mybinder.

When sharing a storage disk between users, as is usually the case in a JupyterHub deployment, it is important to put in guardrails so that one user cannot eat up the whole storage capacity from the rest of the users.

A key challenge in the open source space is that projects are often independent and autonomous, with relatively few formal ways to collaborate and coordinate efforts. While this usually isn’t a big deal, it means that there is a missed opportunity to grow the impact of an ecosystem because it requires coordinated development among multiple stakeholders within it.

We are excited to announce that all 2i2c hubs now run JupyterHub 5.0! This is an upgrade that brings some exciting new features and improvements. Some of the highlights include:

In this post, we’re sharing our Commitment to Open Technology. It is focused on software licenses for reasons we’ll describe below. We hope that it clarifies what kind of licenses we’ll use, and assures our communities that we will not change our stance towards open source technology in the future.

A non-exhaustive list of things 2i2c and Development Seed did with the NASA VEDA project last quarter! Automated backups and alerting with jupyterhub-home-nfs # Tracking Issue jupyterhub-home-nfs is a young project to provide flexible per-user home directory limits on JupyterHub - an important feature for controlling cloud costs.

We are proud to share that several of 2i2c’s community partners are presenting their work at AGU 2024! In each case, 2i2c’s infrastructure plays a part in helping communities create and share knowledge, and grow their community.

2024 has been a busy year for 2i2c, with many highs and lows, a lot of impact, and significant organizational change. As the year comes to an end, I want to reflect on the work we’ve done in 2024, and where we aim to go in 2025.