this post was submitted on 12 Aug 2025
56 points (93.8% liked)

Selfhosted

50502 readers
475 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I've been asked to set up a server for a research team at my university. I've already had the practice of setting a server at home, so I have a rough idea of how things should be done. Still, I wish to follow best practices when setting up a server for this use case. Plus I would prefer to avoid too much tinkering for the setup since I'm planning to keep the installation as simple as possible.

Following are some rough constraints and considerations for the setup:

  • Server computer is a Mac Mini (latest model I think?). I've been told they would replace macOS with Linux, still I believe I should ready if they don't (I don't have experience with macOS at all)
  • Server will be situated in university and provided a static IP address
  • Team needs remote access to the server, presumably comfortable with using CLI
  • I am unlikely to be permitted access to server myself after setup, so it should be ready to be managed by the team
  • Extra hardware and/or paid software could be arranged but to a limited extent and within reason

I don't think they have really any requirement other than having remote access to the server. I think SSH should suffice, however I was wondering if I could also arrange for backups, GUI server panel etc.

top 50 comments
sorted by: hot top controversial new old
[–] 1995ToyotaCorolla@lemmy.world 17 points 2 days ago (6 children)

I guarantee that if your university IT department knows nothing of this they will not appreciate a shadow IT device set up on their network when they find it. And they WILL find it. Reach out to your school’s IT team and make sure your research team has approval to do this before proceeding

Source: worked in Higher Ed IT

load more comments (6 replies)
[–] frongt@lemmy.zip 49 points 3 days ago (14 children)

Step one is check with the university IT department. Don't put random unmanageable shit on other people's networks.

Why a Mac running Linux? I can't think of a use case for that.

[–] aubeynarf@lemmynsfw.com 3 points 3 days ago

probably because they already own it.

[–] m@social.tthi.as 2 points 3 days ago

100% this. After a couple of decades working in universities, I can tell you it's a research integrity issue just waiting to happen - especially if they’re working with human data. Who’s going to be doing the ongoing maintenance? Installing updates? Making sure that nobody pokes holes in the security? What’s going to happen to the data on the server when the funding runs out?

load more comments (12 replies)
[–] Hello_there@fedia.io 21 points 3 days ago (1 children)

You could tell him he needs RAM and a CPU too but they sound like they are at a skill level where they have a grasp on first principals and essential basics.

[–] thecoffeehobbit@sopuli.xyz 5 points 2 days ago

Huh.

There's a time and place for a DIY solution and academia can well be like that sometimes.

The latest Mac Mini can't run Linux though. It's M4 and asahi doesn't even support M3 chips yet. But if you actually got the previous model with M1/M2 you can do Linux if desired. I might not attempt, and just use the Mac as a server as-is. It's not too different from Linux. Asking the duck for "how to xx on Mac" when you already know the Linux equivalents should make your life tolerable.

[–] littleomid@feddit.org 10 points 3 days ago (1 children)

Oof. Do you have any experience doing stuff like this? If you don’t, I don’t think you should take this job. If you know what you’re doing however, then I don’t understand many of your questions. What is the DHCP and firewall situation at the Uni? What is your backup solution? Why will you not have an access key after setup? If there is another team also managing it? What do they think?

In any case, I would NOT use a Mac as a server. You can run Asahi or such on it, but many of our idioms just don’t work on Mac.

If it’s from a Uni and power consumption and Noise don’t matter, I would buy (consciously) three used 1u servers and cluster two proxmox nodes. On the third I would run a proxmox backup server. If money also doesn’t matter, I would do the same, but buy new.

However, you may not even need proxmox, but the issue is that you don’t even know what they are going to use the server for. This makes it impossible for us to give you good suggestions.

[–] bergetfew@sopuli.xyz 2 points 3 days ago (1 children)

I was proposed to set up the server knowing that I have limited knowledge on managing stuff like this. They already have an sysadmin in the campus, but I think their setup is simple enough that they were willing to approach me. Besides I do consider myself to be experienced enough to work my way around CLI and troubleshoot issues even if I haven't had experience with hardware like this.

I don't think negotiating for a different computer would be possible. The main challenge would be to make best of the hardware I'm provided, with additional peripherals if needed.

I do plan on asking them the nature of the work to be done on the server, but I wouldn't expect it to be too niche or computationally intensive since they have separate computers for that. In any case, I will relay the points highlighted in this thread to them and get a clear idea of what is needed to be arranged.

[–] possiblylinux127@lemmy.zip 1 points 2 days ago

How big is the university?

[–] a1studmuffin@aussie.zone 15 points 3 days ago (1 children)

I think you really need to talk to the research team to find out what they want to use the server for, and how they want to collaborate. That will inform everything else.

[–] bergetfew@sopuli.xyz 2 points 3 days ago (2 children)

Part of the reason why they left so many details vague was to give me some freedom on what to setup in the server based on what I think is right, although I do agree there needs to be clarification for some points.

Could you give me a hint on what I should additionally ask regarding their server needs?

[–] a1studmuffin@aussie.zone 3 points 2 days ago* (last edited 2 days ago) (1 children)

I guess as a starting point most of us in this thread don't really know what university research teams do.

If they had a laptop or phone, what kinds of things would they want to do that requires a server? Will they need email? Instant messaging? File sharing? Document collaboration? Will there be sensitive information? Do they need specific software? Or put another way, without this server, what can't they do?

If you can give some hints on that kind of stuff, I'm sure people in this thread can help out more with specifics on software/tech recommendations.

Edit: obviously Unreal Tournament is non-negotiable.

[–] bergetfew@sopuli.xyz 2 points 2 days ago (2 children)

I wasn't able to get a clear response but I can say that they are primarily going to use it for writing and storing code like a Github repo, plus installation of 2-3 programs whose names I couldn't recognise.

They could use Github itself, but I know they know this too so but deliberate chose to work this way. I could probably suggest a software like Gitea or Forgejo for this purpose, but I suppose they aren't in need of that.

[–] possiblylinux127@lemmy.zip 2 points 2 days ago

Github doesn't need a server. It is a cloud service.

Why can't they run the programs locally?

[–] brucethemoose@lemmy.world 1 points 2 days ago

I wasn’t able to get a clear response but I can say that they are primarily going to use it for writing and storing code like a Github repo, plus installation of 2-3 programs whose names I couldn’t recognise.

This makes sense. Sometimes its better to run 'helper' programs in a remote container so configs and such are synced.

If they are trying to setup an inference server for cursor or something, though, you will need to run OSX. Linux does not support Metal acceleration (last I checked).

[–] possiblylinux127@lemmy.zip 1 points 2 days ago

I think step 1 would be to see if they need a server.

[–] Agility0971@lemmy.world 6 points 2 days ago* (last edited 2 days ago)

Usually you ask IT department to spin up a vm for you. They will take care of security and backups.

[–] ptmb@lemmy.zip 7 points 3 days ago

If they really didn't provide you any more information than what you mentioned in the post and comments and you won't even be permitted access to maintain the server, I wouldn't complicate too much. Even if you could do more, you'd be guessing, and probably make life harder for the researchers who might not have the expertise having to actually maintain something too complex.

Do the bare minimum to make it functional and overall secure, make sure the operating system works, get SSH access configured for as few people as you can get away with, and make sure updates are installed automatically. They should be responsible for everything else and you should make that clear to them (backups, software, etc)

Provide notes on what you did to the future owners of the server and maintenance instructions as well.

If you are part of an IT team in the university, and if you have some leverage on it, make sure you have the authority to handle things on an emergency (like having the right to pull the plug if the server becomes rogue or misbehaves somehow). Also look to see if you can push them to a more standardized alternative, if your IT team provides standard services look to see if their use case can be fulfilled somehow by them, even partially. I know a lot of universities provide code forges and job submission clusters students and teachers can use, maybe their use case fits these.

[–] thejevans@lemmy.ml 6 points 3 days ago (1 children)

Will they need to install new software after you set it up, or just have user storage and maybe do system updates?

What will they be doing with it?

Do you have a backup storage location available?

How many users?

What kind of permissions do they want various users to have?

How critical is the data that will be housed on the server?

[–] bergetfew@sopuli.xyz 1 points 3 days ago* (last edited 3 days ago) (3 children)

Sorry if I am unable to provide specific details for the queries. I don't have answers to most of them myself which is why I was hoping what the safest bet for these situations would be to implement.

  1. Highly likely they would be installing new software

  2. I don't know much about its use case, although it won't be too intensive since they probably have a separate machine for heavier work.

  3. Backup storage option wasn't proposed at all. I'm thinking of proposing to implement one.

  4. I expect between 10-20 users.

  5. User permissions requirements wasn't discussed as well, although I wouldn't expect there to be any need to grant everyone admin privileges

  6. Don't know about the criticality of data. I could only speculate to be considerable by default.

[–] thejevans@lemmy.ml 3 points 2 days ago

Highly likely they would be installing new software

This basically means that the system will rot over time and will need to have someone who knows what they're doing to maintain it. If they don't know enough to do the initial setup, then I would worry about how quickly it would go awry after you no longer have access. given the number of users and the assumed criticality of the data, I would have a long conversation about what can happen and what their plans are

[–] possiblylinux127@lemmy.zip 2 points 2 days ago

I personally would not do this. There are so many red flags.

[–] rainwall@piefed.social 5 points 3 days ago* (last edited 3 days ago) (1 children)

Backup is step one, or even step 0, of setting up a server. The amount of frustration and even job loss a backup can prevent is always worth the expense of time/money.

Backup can be setup scripts/config files/automation if the data doesnt matter, but you do need it. Also, even if they say the data doesn't matter, the data almost always matters. It may not now, but it will in 3 years when people use the server for real work and everyone just doesnt even begin to think about a backup until the server fails one day and they lose years worth of their grant and thesis data.

Backups can be simple, they can be complex. They can be free or pay, they can have gui or just be scripts. Settle on one that you can make work, and CHECK THEM OCCASIONALLY with test restores of at least a few files. If you dont test and find a working backup, you have hope, not resiliency.

[–] bergetfew@sopuli.xyz 1 points 3 days ago (1 children)

Could you suggest what would be the most appropriate backup solution in this case? I could also ask them to arrange a backup drive or a cloud provider if needed.

[–] rainwall@piefed.social 1 points 2 days ago

Depends on what you're doing a bit. Databases? Hypervisors? Just files? If all of the above, its best to use an actual product this. Either foss like borgbackup or Urbackup, or something like Veeam which is a popular pay option.

If its a proxmox hypervisor, they have their own free backup appliance, but you need a second physical server to run it on.

If it's just databases, most have a built in way to take a backup. Just google the name and backup. Make sure it's running automatically and is moved to a separate server on each run.

For files, rsync is a great option.

[–] CocaineShrimp@sh.itjust.works 5 points 3 days ago (1 children)

I know this isn't exactly what you're asking for, but I'd recommend also looking into a VM OS such as proxmox or unraid (I'm running unraid)

They'll let you create/destroy VM instances you can access remotely. So in theory, you can give everyone their own VM to use and access the files on the server.

However, unraid / proxmox may have performance issues running in a VM on a Mac mini...

[–] illusionist@lemmy.zip 3 points 2 days ago (1 children)

What do you need (temporary) VMs for?

[–] CocaineShrimp@sh.itjust.works 2 points 2 days ago* (last edited 2 days ago) (1 children)

I was thinking OP could give everyone their own VM to use as a workstation so they could access the files on the server easily, and/or run programs based on their work. When their coworkers leave, OP can easily destroy the VM and the resources would be automatically reallocated (depending on the servers configuration). With a physical device, the storage on that device is only allocated to that device and can't be shared when it's not in use

Me, personally? I have multiple VMs for different contexts: my teaching job (super clean, video sharing tools, presentation tools), gaming, media server (has scripts to download stuff off of YouTube), server management (just a regular Debian install), and a fuck around box (I just use it to try new OSs like Fedora, or try breaking OSs like deleting the system32 folder on windows)

[–] illusionist@lemmy.zip 1 points 2 days ago* (last edited 2 days ago)

Ok, good reasons. I would've thougut about vacode, rstudio server, et al so that you really only have a server. I hate not having a sound card on a remote windows server

[–] dil@lemmy.zip 2 points 3 days ago

Im confused, we had servers at our school, it can be whatever thats accessible over ssh, but should also only be accessible through school vpn/network, guess thatd be the default if its stored at the school. Maybe make sure it has wake on lan for convenience. Btrfs snapshot for easy reversals.

[–] aubeynarf@lemmynsfw.com 2 points 3 days ago

use some file system with snapshots and differential backups, like ZFS, and snapshot it daily. Stream the diffs somewhere they can’t login to and which doesn’t mount the FS.

This will invariably save their bacon at some point.

load more comments
view more: next ›