Configure pip for DataSurface

Configure pip for DataSurface PyPI registry across Linux, macOS, Windows, and CI/CD.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/billynewport/demo_cokub_model --skill configure-pip-for-datasurface
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Configure pip for DataSurface
Source: https://github.com/billynewport/demo_cokub_model/tree/main/.claude/skills/configure-pip-datasurface
Command: npx skills add https://github.com/billynewport/demo_cokub_model --skill configure-pip-for-datasurface

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill configures a persistent PyPI index for DataSurface access, eliminating the need to repeatedly supply credentials and index URLs when installing.

Core Features & Use Cases

  • Centralized authentication: configures a persistent PyPI index for DataSurface from GitLab Packages using pip.conf, pip.ini, or environment variables.
  • Flexible deployment options: supports Linux/macOS, Windows, and CI/CD workflows (GitHub Actions and GitLab CI) for seamless integration.
  • Use Case: A data engineer working in a corporate Python environment can configure a single pip source so that subsequent pip install datasurface works without embedding credentials in each command.

Quick Start

Use one of the supported methods to configure pip to access the DataSurface GitLab registry. Examples include:

  • Linux/macOS: create ~/.pip/pip.conf with an extra-index-url referencing the DataSurface registry using your credentials.
  • Windows: create %APPDATA%\pip\pip.ini with the extra-index-url setting.
  • CI/CD: set PIP_EXTRA_INDEX_URL or use a pip.conf in the runner to supply credentials securely.

Frequently Asked Questions about Configure pip for DataSurface

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure pip to install packages from a private GitLab PyPI registry?

To configure pip for a private GitLab PyPI registry, you can set an extra-index-url in your pip.conf or pip.ini file, embedding your credentials so subsequent pip install commands authenticate automatically.

What is the best way to persist DataSurface credentials for pip across CI/CD workflows?

Persisting DataSurface credentials in CI/CD workflows is best handled by setting the PIP_EXTRA_INDEX_URL environment variable or using a secure pip.conf file in the GitHub Actions or GitLab CI runner.

Does pip.conf work the same way on Windows and Linux for private index authentication?

pip.conf works similarly across platforms, but the file location differs: Linux and macOS use ~/.pip/pip.conf, while Windows uses %APPDATA%\pip\pip.ini to store the extra-index-url and authentication settings.

How do I stop passing credentials explicitly every time I run pip install?

You can stop passing credentials explicitly by creating a persistent pip configuration file with the extra-index-url pointing to your DataSurface registry, allowing pip install to work without embedded command-line credentials.

Can I use environment variables instead of pip.conf to authenticate to a private PyPI index?

You can use environment variables instead of pip.conf by setting PIP_EXTRA_INDEX_URL with your DataSurface registry credentials, which is especially useful for securing authentication in ephemeral CI/CD environments.