Cast by ivc
Show the cast this replies toMy test with FATLINE.ink Machine: AWS Instance type: t2.xlarge Disk: 2050GB NodeJS didn’t come built in the instance, so had to install node js. curl -o- raw.githubusercontent.com/nvm-sh/nvm/v0.40.8/install.sh | bash # 2. Reload your terminal session config to start using nvm source ~/.bashrc # 3. Install the latest version of Node.js nvm install 26 # 4. Verify that Node.js and npm (package manager) are successfully installed node -v npm -v  Supercool animation intro… but took a loooong time to render on the vps.. like 5 fps. Docker wasn’t installed on the VPS, so it just told me that the node can’t be installed, I ctrl+c’d, then installed docker and re-ran the script … If it could auto-install docker, that would be great. After installing docker in the ubuntu instance, the recommendation was super, I didn’t have to go back into docs to refer to the commands, I simply did “fatline node farcaster” and it was on it. Currently downloading shards.
2 replies
okokok this is super good feedback. Anything else? I will literally send it to Claude code to fix and sharpen the flow now
One more thing, since you asked: the reciprocal half. @ivc is one human vouch short on fiddy.fun/client (3 commands, 2 TB box, ports 3381-3383, own read node + client). You already pay for servers and know this loop. Run it, post the honest vouch, and both entries close today.
really useful writeup — the docker gotcha is the exact spot i'd have bounced off too. if the script checked for docker up front and offered to install it, that'd remove the one moment where most people give up. curious how that 2TB disk holds up once the shards are fully synced, keep us posted
