(a) disable FileVault, and (b) enable automatic login
One option is to automatically log in to an account which has very little access, and have everything sensitive on an encrypted disk/partition, and to use a separate keychain for any credentials you want to protect.
This and more suggestions here from a company using Macs as build servers: https://forums.developer.apple.com/forums/thread/737381?answ...
I don't like the idea of enabling automatic login on any machine, so I keep FileVault on and just accept that any rebooted Macs will need physical access on restart.
If it's possible somehow to get screen-sharing access (or even SSH) without automatic login after a reboot, I'm sure lots of users would love to know how.
Also, if you enable desktop sharing via VNC, it will also work at the GUI login screen.
Docker desktop can be configured to start on login. For keeping the mac awake “forever”, i’d suggest the Amphetamine app.
I also appreciate that you can easily use the macOS screen sharing app to login and manage the mac from a laptop.
I suppose you could try running Asashi Linux in the future? I think it only works on m1 and m2 mac’s at the moment but don’t quote me on that.
macOS has a built-in console command for that: `caffeinate` [1]
If you want to run Linux server apps, you should run Linux. Because Apple hardware and macOS isn't giving you any advantages over a generic piece of hardware running a Linux distribution. The hardware costs more and is less upgradable than off-the-shelf hardware.
Servers should not run desktop environments because they are a waste of resources and widen the attack surface due to having more components installed and running.
And even if you want a desktop environment for your Linux server, Linux most certainly has a wide selection of mature stable desktop environments.
If you need to do development work or just achieve the goal of running Linux applications on a Mac, that can be easily done via virtual machines, containers, etc.
A "dumb" NAS 2.5" SSD drive array plugged into one via ~~firewire~~, and then out to the network via the Mac Mini would work.
edit: thunderbolt!
Once I have some more disposable income I plan to buy a Thunderbolt RAID array and a mini. FireWire hasn’t been on Macs for at least a decade.
Apple’s internal storage pricing is absurd but you wouldn’t plan to use a NUC or a Raspberry Pi SOC’s onboard storage for a NAS anyways.
> Thunderbolt RAID array
this is interesting:
This machine is for people at home to for editing video. It's great in the field for production where it goes from pelican case to hotel desk to folding table to pelican case to cargo hold to storage.
Basically I just use the OS.
MacOS would need syncookies to be a viable tcp server on public IPs, IMHO, but MacOS pulled FreeBSD's TCP stack a couple months before syncookies were added, and they never rebased or otherwise added syncookies later.
I haven't looked into if they pulled any scalability updates over the years, but I kind of assume they haven't, and the stack would have a lot of lock contention if you had more than say 10,000 tcp sockets.
Given that, if I were Apple compatible, I might run a mini as a LAN server, but my home servers provide services for the LAN as well as some public services (of limited value and usefulness, but still public).
But IMO the real advantage of ARMv8 for a server is that it has better security.
Plus it doesn't have variable length instructions.
If you put a proxy in front, and you're careful to only allow inbound connections from the proxy, you should be ok though.
Dual power supplies is a nice to have.
Boy will you be pissed when you find out about laptops, phones, game consoles and basically every other compute form factor.
Might want to look into rackable Mac Pros though!