20260212 Weekly Development Meeting

[josecelano]

• Time:

  • 09:30 in Canary Islands (WET / UTC+0)
  • 10:30 in Vaduz (CET / UTC+1)

• Location:
  https://meeting.blockfinance-eco.li/nautiluscyberneeringweeklydevmeeting

• Expected Duration: 2 to 4 hours, including breaks

• Confirmed Attendees:

  • Cameron Garnham (@da2ce7)
  • Constantin Bosse (@cgbosse)
  • Jose Celano (@josecelano)

---

Agenda

1. Weekly Updates (Each participant will take a turn)

Each team member should come prepared with comments added in advance to this discussion. During their turn, they will:

• Review their notes/comments and provide a summary of:
  • Issues worked on
  • Progress made
  • Other relevant tasks completed
• Share any challenges faced and request assistance if needed
• Highlight any difficulties that may risk delays or affect the final product's quality
• Outline their planned tasks for the upcoming week
• Mention any new technical topics they've noted for potential future discussion (to be added as comments in this thread)

🔁 This format ensures everyone follows a structured sequence during the meeting.

2. Technical Discussion Planning

After all updates:

• Any proposed technical topics will be reviewed
• A decision will be made on whether to:
  • Schedule a follow-up technical meeting, or
  • Continue with the discussion immediately, time permitting
• The attendees for the follow-up meeting will be determined, allowing others to resume their work as needed

[josecelano]

Torrust Tracker Deployer

This week, I have been working on roadmap issues and other minor tasks.

• Roadmap torrust/torrust-tracker-deployer#1
  • Extend deployer usability (9)
    • Implement artifact generation command torrust/torrust-tracker-deployer#326 (9.2)
  • Improve usability (UX) (10)
    • Add DNS Setup Reminder in Provision Command torrust/torrust-tracker-deployer#332 (10.1)
    • Improve Run Command Output with Service URLs torrust/torrust-tracker-deployer#334 (10.2)
    • Add DNS Resolution Check to Test Command torrust/torrust-tracker-deployer#336 (10.3)
    • Add Purge Command to Remove Local Environment Data torrust/torrust-tracker-deployer#322 (10.4)
  • Improve AI agent experience (11)
    • EPIC: Adopt Agent Skills Specification torrust/torrust-tracker-deployer#274 (11.1)
      • Infrastructure Scaffolding and Foundational Skills torrust/torrust-tracker-deployer#320
      • Added some skills.
    • Provide Configuration Examples and Questionnaire for AI Agent Guidance torrust/torrust-tracker-deployer#339 (11.3) WIP

Refactors:

• refactor: split tracker_ports.rs into focused submodule torrust/torrust-tracker-deployer#319

Maintenance:

• Update Docker base images to latest stable releases torrust/torrust-tracker-deployer#317

Bugs:

• Ansible playbook deploys .env and docker-compose files as root:root instead of ansible_user torrust/torrust-tracker-deployer#313

CI:

• Add E2E Test Workflow for Dependency Installer torrust/torrust-tracker-deployer#330

Testing:

• Clean up E2E deployment test state after successful test run torrust/torrust-tracker-deployer#324

NOTE: Total time spent on Torrust ~27.5h

We can discuss whether we should implement the remaining tasks:

• Add levels of verbosity (section 8 in roadmap)
• Add dry-run mode for all commands (task 11.4)
• I would like to implement the JSON output format at least for the "show" command because agents do this to get the instance IP:

# Set environment name and get IP from environment state
export ENV_NAME="your-environment-name"
export INSTANCE_IP=$(cat data/$ENV_NAME/environment.json | jq -r '.Running.context.runtime_outputs.instance_ip')

The problem is there is no easy way to parse the IP from the public output becuase it's not a structured format. LLM can get the value, but it can't build an easy script to parse it, so it gets it from the internal state, which is a JSON file. The problem is that the documentation is full of this trick, and it couples the documentation with the internal state, making it harder to refactor the internal state if we want.

The JSON output format was excluded from this roadmap. I was planning to include it in future releases.

I decided to start with the human-friendly version of the output, and that was a mistake. I thought it was easy to parse the output for AI agents, and it is, but it's not easy to manipulate that output to chain it with other actions :-(. Anyway, the code is structured so that adding new formats is really easy.