Selfhosted

61512 readers

1319 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Setting up a server for a research team. What should be in my checklist? (sopuli.xyz)

submitted 1 year ago by bergetfew@sopuli.xyz to c/selfhosted@lemmy.world

45 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

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

Mostly it boils down to laziness. They for sure have the ability to set up the server themselves but they can't be bothered to unless it's for a larger number of machines. They have essentially given a thumbs up to proceed with the setup but haven't offered assistance themselves. I think the team might already have reached out to them, but were let down which is why they tried to contact me.

The server will be stored in the personal office of one of the members of the team. It should be physically secure.

I don't think I would completely lose access to it, rather it's just that I won't be allowed to personally SSH to the server with my own devices. I may still be able to connect to it through one of the members' devices or onsite. The team member earlier mentioned will take care of the system after the setup.

I don't know what'll happen to the server after the project is over, nor am I in a position to assume something.

[–] possiblylinux127@lemmy.zip 4 points 1 year ago

Why do you want to help lazy people? You are most certainly going to regret getting yourself into this.

[–] tko@tkohhh.social 2 points 1 year ago

Have you personally asked the IT department about this? I would be concerned that they were told "no" by IT, so they are asking you to do it behind their back.