feat: pip package deployment mode for python type

[nilshamerlinck]

Summary

• python type now supports deploying directly from a pip package instead of cloning a repo — controlled by the requirements key in deploy.yml
• requirements and repo_url are mutually exclusive; a list or single string are both accepted
• configure creates the instance directory, sets up a venv, and runs uv pip install
• update runs uv pip install --upgrade instead of git pull
• python.service.j2 now includes EnvironmentFile=-<instance_path>/.env so a .env is loaded automatically if present

Example config

service-myapp-production:
  type: python
  ssh_host: myserver.example.com
  requirements:
    - "myapp==1.2.3"
    - "some-dep>=2.0"
  exec_start: "myapp serve"

Test plan

• configure with requirements → creates dir, venv, installs packages, registers systemd unit
• configure with repo_url → existing clone behaviour unchanged
• configure with both requirements and repo_url → error
• update with requirements → upgrades packages and restarts service
• update with repo_url → git pull behaviour unchanged
• Service picks up .env when present; starts normally when absent

🤖 Generated with Claude Code

[nilshamerlinck]

hi @hailangvn I have a vague memory that we decided against 7bf3346 at some point but I can't remember why, do you?

[hailangvn]

LGTM. Thank you.

[hailangvn]

hi @hailangvn I have a vague memory that we decided against 7bf3346 at some point but I can't remember why, do you?

No, I don't remember that we discuss about it.