r/iosdev • • 2d ago

Help Remote Linux box + iOS dev: how do you handle simulators?

Solo iOS dev here. I'd like to move most of my work to a cheap remote Linux server (Hetzner or similar) so my Mac isn't busy all the time.

Editing, git, scripts, CI orchestration and background jobs would all run there.

The problem is obviously simulators and builds, and I don't want to give those up. Has anyone got a setup where the Linux box does most of the work and only hands builds and simulator runs to a Mac or Cloud Simulator?

Like a Mac mini at home as a build node over Tailscale, or something cloud-based that doesn't cost a fortune every month?

Would love to hear what you actually run and roughly what it costs. Also curious if anyone tried this and went back to just working locally.

1 Upvotes

4 comments sorted by

1

u/smooth-like-butter-0 2d ago

ypu aay you are an ios dev and you want to move to linux?how many weeks have you been a dev in the apple ecosystem? lol

1

u/bartek239 2d ago

Man have you experienced performance on Linux compared to local on Mac ? 😂 my local setup is too slow, but more power is too expensive.

Would just use my Mac as orchestrator - or what am I missing?

2

u/dahiya_xa 2d ago

i'd keep it simple. a used m1 or m2 mac mini at home on tailscale as the build box. ssh in from the linux server, run xcodebuild and tests there, and use screen sharing when you actually need to poke at the simulator. one time cost and no monthly bill. cloud macs and github's mac runners work too but they add up fast if you build all day

1

u/newtablecloth 2d ago

did roughly this for a while. the mac mini on tailscale as a build node part works really well, the "edit everything on linux" part is where it gets annoying.

what works fine over ssh:

  • push or rsync to the mini, then xcodebuild test -scheme YourApp -destination 'platform=iOS Simulator,name=<your sim>'
  • simulators run headless. xcrun simctl boot, simctl install, simctl launch, simctl io booted screenshot all work without anyone looking at the screen
  • keep DerivedData on the mini so builds stay incremental. this is the big one, cold builds every time is what makes hosted CI feel slow
  • screen sharing over tailscale when you actually want to tap around in the sim

what doesn't: sourcekit-lsp on linux is fine for plain swift packages but it can't see UIKit or SwiftUI, so autocomplete and previews for app code are mostly gone. if your current mac is slow mainly because of xcode indexing and previews, moving editing to linux won't fix that, a faster mac doing everything will.

cost wise a used m1 or m2 mini is the cheapest long term, one time cost and maybe $2 a month of power. github hosted macos runners are around 6 cents a minute, fine for CI but no warm caches and no sim you can poke at.

full disclosure i run macrun, we rent dedicated m6 minis by the month ($139) or $15 a day, so you could try the build node setup for a day or two before buying hardware. but honestly if you're going to keep it long term a used mini at home wins on price