Selfhosted

40183 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 1 year ago

MODERATORS

[email protected]

112

How responsive is your Nextcloud? (sh.itjust.works)

submitted 8 months ago* (last edited 8 months ago) by [email protected] to c/[email protected]

75 comments fedilink hide all child comments

My Nextcloud has always been sluggish — navigating and interacting isn't snappy/responsive, changing between apps is very slow, loading tasks is horrible, etc. I'm curious what the experience is like for other people. I'd also be curious to know how you have your Nextcloud set up (install method, server hardware, any other relevent special configs, etc.). Mine is essentially just a default install of Nextcloud Snap.

Edit (2024-03-03T09:00Z): I should clarify that I am specifically talking about the web interface and not general file sync capabilites. Specifically, I notice the sluggishness the most when interacting with the calendar, and tasks.

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

[–] [email protected] 4 points 8 months ago (7 children)

Have you read my comment? It's about where the packages and services are installed.

In this case, they're installed in the container, not on the host

[–] [email protected] 7 points 8 months ago* (last edited 8 months ago) (5 children)

What is it you think the "metal" is in in the phrase "running on bare metal?"

Your comment is irrelevant. Who cares in what directory or disk image the packages are installed? If I run in a "chroot jail" am I not "running on bare metal?" What if I include a library in /opt/application/lib? Does it matter if the binaries are on an NFS share? This is all irrelevant.

The phrase means to be not running in any emulation. To answer my question above - the "metal" is the CPU (edit: and other hardware).

edit2: I mean - it's the defining characteristic of containers that they execute on bare metal unlike VMs and (arguably - I won't get into it) hypervisors. There is no hardware abstraction at all. They just run natively.

[–] [email protected] -2 points 8 months ago (4 children)

It's just what it means in this specific context.

They're not running directly on the host, with directly meaning directly.

If you go by definition, I agree with you, but the definition is not always the thing to go off of.

[–] [email protected] 1 points 8 months ago

Is docker virtualized or otherwise emulating something? It's just a way to package things, like an installer? Then it's bare metal.

I had to look this up too, I thought docker containers were virtualized.

load more comments (3 replies)

load more comments (4 replies)