Template

Files

lmiranda 8bb69d3556 feat: project refactoring - folder cleanup, governance, and automation

Project Structure Cleanup:
- Remove deprecated cmdb-assistant plugin
- Remove development output files (test scripts, status reports)
- Remove IDE-specific workspace files
- Create scripts/ directory for automation
- Create docs/architecture/ for Draw.io diagrams
- Create docs/workflows/ for workflow documentation
- Create .scratch/ directory for transient work

Governance & Documentation:
- Add File Creation Governance section to CLAUDE.md
- Add architecture diagram specifications (component-map, agent-workflow)
- Add docs/UPDATING.md with update workflow
- Update CHANGELOG.md with all changes

Installation Automation:
- Add scripts/setup.sh for initial installation
- Add scripts/post-update.sh for updates after git pull
- Add /initial-setup slash command

Maintenance:
- Update .gitignore with scratch directory
- Fix all project name references (use support-claude-mktplace)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-11 22:17:27 -05:00

2.3 KiB

Raw Blame History

Updating support-claude-mktplace

This guide covers how to update your local installation when new versions are released.

Quick Update

# 1. Pull latest changes
cd /path/to/support-claude-mktplace
git pull origin main

# 2. Run post-update script
./scripts/post-update.sh

What the Post-Update Script Does

Updates Python dependencies for Gitea and Wiki.js MCP servers
Shows recent changelog entries so you know what changed
Validates your configuration is still compatible

Manual Steps After Update

Some updates may require manual configuration changes:

New Environment Variables

If the changelog mentions new environment variables:

Check the variable name and purpose in the changelog
Add it to the appropriate config file:
- Gitea variables → ~/.config/claude/gitea.env
- Wiki.js variables → ~/.config/claude/wikijs.env
- Project variables → .env in your project root

New MCP Server Features

If a new MCP server tool is added:

The post-update script handles dependency installation
Check docs/references/MCP-*.md for usage documentation
New tools are available immediately after update

Breaking Changes

Breaking changes will be clearly marked in CHANGELOG.md with migration instructions.

Troubleshooting

Dependencies fail to install

# Rebuild virtual environment
cd mcp-servers/gitea
rm -rf .venv
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
deactivate

# Repeat for wikijs
cd ../wikijs
rm -rf .venv
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
deactivate

Configuration no longer works

Check CHANGELOG.md for breaking changes
Compare your config files with updated .env.example (if provided)
Run ./scripts/setup.sh to validate configuration

MCP server won't start

Check Python version: python3 --version (requires 3.10+)
Verify venv exists: ls mcp-servers/gitea/.venv
Check logs for specific errors

Version Pinning

To stay on a specific version:

# List available tags
git tag

# Checkout specific version
git checkout v1.0.0

# Run post-update
./scripts/post-update.sh

Getting Help

Check docs/references/ for component documentation
Review CHANGELOG.md for recent changes
Search existing issues in Gitea

2.3 KiB Raw Blame History