This weekend I was playing around with the IBM Bluemix platform at the SpaceApps Challenge in Glasgow.
The tools provided made deploying the team’s Node.js application fairly simple but now it’s time to clean up — I don’t want to have a bunch of stuff I don’t have a use for kicking around on my Mac.
Getting shot of the Cloud Foundry CLI application was easy (not least because they provide instructions but also because it’s easy to put the cf binary somewhere useful and just bin it when you’re done) but the BlueMix CLI itself was more tricky (they use an installer .pkg; there didn’t seem to be any clear uninstallation instructions). So here’s what I’ve worked out from extracting the installer .pkg and poking around in the postinstall script:
Delete the bluemix binary by running:
sudo rm -rvf /usr/local/Bluemix/
sudo rm -v /usr/local/bin/bluemix
sudo rm -v /usr/local/bin/bx
From /etc/profile, remove:
### Added by the Bluemix CLI
source /usr/local/Bluemix/bx/bash_autocomplete
From ~/.bashrc, remove:
### Added by the Bluemix CLI
source /usr/local/Bluemix/bx/bash_autocomplete
From ~/.zshrc, remove:
### Added by the Bluemix CLI
source /usr/local/Bluemix/bx/zsh_autocomplete
Some of these may not exist — the installer script does at least check whether they do before appending to them.
Both cf and bluemix store config data in the home directory (in ~/.cf and ~/.bluemix respectively) — if you don’t care about keeping that, it should be safe to delete too.