Lab #1202: ln: failed to create symbolic link '/usr/local/bin/swamp': No such file or directory

ran the installer. It failed because ... not all Linux boxes have /usr/local/bin/ pre-created. This being a newly installed computer ... you'd need to detect this and call mkdir -p /usr/local/bin/ -

--- Downloading and installing 'swamp' release 'stable' on 'linux-x86_64'

Downloading https://artifacts.swamp-club.com/swamp/stable/binary/linux/x86_64/swamp-stable-binary-linux-x86_64.tar.gz to /tmp/tmp.ccnyGkISnG/swamp-stable-binary-linux-x86_64.tar.gz (curl)
Following S3 redirect to https://artifacts.swamp-club.com/swamp/20260716.235126.0-sha.df18185b/binary/linux/x86_64/swamp-20260716.235126.0-sha.df18185b-binary-linux-x86_64.tar.gz --- Extracting 'swamp-stable-binary-linux-x86_64.tar.gz'
Extracting archive ... done. --- Installing 'swamp'
Installing '/home/sven/.swamp/bin/swamp' ... done.
Symlinking '/home/sven/.swamp/bin/swamp' to /usr/local/bin/swamp [sudo required to link swamp under /usr/local/bin] Password for sven: ln: failed to create symbolic link '/usr/local/bin/swamp': No such file or directory

workflow placement: run a workflow transparently on a specified host, local or via swamp workers (incl. nested child workflows)

deprecated extensions are more prominent than I expected :)

swamp serve daemon (user service) doesn't handle systemd 'lingering' — claims it 'starts automatically' but only runs while logged in

Trigger schedule overrides require a swamp serve restart to take effect

swamp serve daemon (user service) doesn't handle systemd 'lingering' — claims it 'starts automatically' but only runs while logged in

swamp cmds don't realise the user is sshed into the system

swamp issue bug isn't auto-filling swamp version, OS and shell

Upgrade/Update causes odd locking issue on swamp deno

stale lock file not being cleaned up?

swamp auth login process fails when run remotely

can the combat log also tell me which hostname the command was run on?

add links to the docs for all account progress teasers

ExtensionWorkflowRepository scans manifest.yaml as a workflow, emitting 'Unknown key manifestVersion' warning

Swamp serve daemon doesn't run with --hot-reload

I _think_ I might like a guard in the trigger yaml

swamp command doesn't check cwd

Output a log line for steps skipped due to guards

Add a --release-notes option to `swamp update` (or even make it the default)

Running "swamp workflow run ..." in a subdir of the swamp repo fails

Pushing an extension after creating a public git repo that is the same as other previously pushed extensions doesn't update the "Verified public repository"

Could not start dynamically linked executable: /home/sven/.swamp/bin/swamp

ln: failed to create symbolic link '/usr/local/bin/swamp': No such file or directory

Relationships

#1202 ln: failed to create symbolic link '/usr/local/bin/swamp': No such file or directory

Shipped