Private Python packages for your conda environments

# Create and activate your conda environment, with pip in it
conda create --name myproject python=3.12 pip
conda activate myproject

# Credentials go in ~/.netrc, not in the index URL. The login is the email
# of the user who created the repository token, in lower case.
# The subshell's umask keeps the file private from the moment it is created;
# >> adds the entry without replacing an existing ~/.netrc.
(umask 077 && printf 'machine your-org.mycloudrepo.io\nlogin you@example.com\npassword %s\n' \
  "$CLOUDREPO_TOKEN" >> ~/.netrc)
chmod 600 ~/.netrc

# Install conda packages as usual
conda install numpy pandas scikit-learn

# Install private packages from CloudRepo via pip. pip reads the login
# from ~/.netrc
pip install -r requirements-private.txt

--index-url https://your-org.mycloudrepo.io/repositories/your-repo/simple/
your-private-ml-model
company-data-utils==2.1.0

# Keep the pip: section for public packages. Do not put the CloudRepo URL
# or a token in this file: conda installs every line of the pip: section
# with one pip run.
name: data-science-project
channels:
  - conda-forge
dependencies:
  - python=3.12
  - numpy
  - pip
  - pip:
      - requests

conda env create --file environment.yml
conda activate data-science-project
pip install -r requirements-private.txt

# Install build tools
pip install build twine

# Build your Python package
python -m build

# Upload to CloudRepo. twine reads its credential from these variables,
# so the token is not an argument. The username is the email address of
# the account that created the token.
export TWINE_USERNAME="you@example.com"
export TWINE_PASSWORD="$CLOUDREPO_TOKEN"
twine upload --non-interactive \
  --repository-url https://your-org.mycloudrepo.io/repositories/your-repo \
  dist/*