Hey People,
Sorry for asking stupid question but currently I know nothing about Apple and this whole ecosystem.
Currently working on amazing new idea I believe someday will become alive but I need to know how bit interest is there ins this macOS Server?
I know this solution is not for simple ordinary people ;-) so I'm wondering how many of you is using this solution and why.
Thanks for every replay
Raf
Current versions of macOS Server are a package that is best suited for managing devices; an MDM package.
Older versions of Server.app provided mail, chat server, networking, DNS and other network services, though those and other capabilities have been deprecated and are no longer available in the version of Server.app for Mojave, and a few—such as file services—have been migrated into the base macOS distribution.
Typical server boxes now are either hosted services (Amazon, AWS, etc) or hosted systems (Scaleway, Rackspace, Linode, etc)—for those that want or need to maintain their own servers—are running on Linux, BSD or Windows Server configurations and usually on x86-64 or Arm servers.
There are folks that do use macOS—without Server.app—as a server, and one hosting provider is macminicolo. There are some others.
If you're aiming for less management, you're probably going to be installing and booting on an x86-64 or Arm server packaged with whatever operating system distribution might be necessary, and that either booting natively or as a guest in one of the common virtual machines.
But without some specifics on the plan and the requirements, there's little that can be specifically discussed.
Current versions of macOS Server are a package that is best suited for managing devices; an MDM package.
Older versions of Server.app provided mail, chat server, networking, DNS and other network services, though those and other capabilities have been deprecated and are no longer available in the version of Server.app for Mojave, and a few—such as file services—have been migrated into the base macOS distribution.
Typical server boxes now are either hosted services (Amazon, AWS, etc) or hosted systems (Scaleway, Rackspace, Linode, etc)—for those that want or need to maintain their own servers—are running on Linux, BSD or Windows Server configurations and usually on x86-64 or Arm servers.
There are folks that do use macOS—without Server.app—as a server, and one hosting provider is macminicolo. There are some others.
If you're aiming for less management, you're probably going to be installing and booting on an x86-64 or Arm server packaged with whatever operating system distribution might be necessary, and that either booting natively or as a guest in one of the common virtual machines.
But without some specifics on the plan and the requirements, there's little that can be specifically discussed.
There's not a whole lot of need to install network server components atop Linux, BSD or Windows Server.
Server.app used to activate some of what was present in macOS, and would add some tools to macOS, and Server.app added a management GUI.
But most of what Server.app provided has been deprecated with Server.app for Mojave.
Qubes OS isn't multi-user, which'll seemingly make configuring and running it as a network server a more complex task.
It is possible to run various operating systems as guests of Qubes. There's a documented list available, though macOS is not on that list. Is that what you're pondering here? And it's still not clear to me what booting macOS in a Qubes HVM (and necessarily with Qubes OS booted on a Mac) would gain for a macOS user.
Thank you MrHoffman for that great explanation.
My plan is simple and focused mainly on the privacy and this also includes something called "canary"
I need to put macOS server on to Qubes-OS :-)
Just wondering if anyone have done this before
Raf
In this situation this is my misunderstanding and thanks for explanation.
I though this is a package and that could be installed on a top of any other OS
Because Apple is new to me the idea behind my question was to run this macOS Server as isolated appliance in Qubes OS
So thanks again for explanation
Not sure where you're headed here, as Qubes OS is an operating system.
Canaries are a common approach for detecting shenanigans. Thinkst offers some freebies here, for instance.
You'd have to start with Qubes running on Mac hardware, as that's required by the macOS software licensing.
How that integrates with macOS? macOS booted as a guest in a hypervisor hosted within or hosted alongside Qubes OS really doesn't seem to gain anything obvious (to me).
But irrespective of the Server product name, macOS Server is effectively an MDM package atop macOS and not a network server package, and the current Mojave Server.app is not really something I'd expect to find operating in conjunction with Qubes OS. I would expect to find macOS operating as a guest of a hypervisor running on Mac hardware, if not booted natively on a Mac and as is far more common.
macOS Server
