[Feature Request] Disk space from other servers

[benphelps]

Discussed in #22

^{Originally posted by chrisg991 August 27, 2022}
Feature Request:
Please would you add the ability to report free disk space from other servers on the network. Homepage currently displays the disk space, cpu and memory usage of my Docker VM but it would be useful to see those same measures (particularly disk space) for the physical servers on my network.

Thank you

[ShlomiPorush]

you need to mount those disk to the docker vm (in you situation)
i mounted my NASs via smb.
For security concerns, you can mount them as read-only... and that's indeed what I did.

[Smiggel]

How can I mount drives using the stack? Tried it, but getting errors all the time that it's not allowed.

[benphelps]

Pretty much every feature and configuration option needed is documented in the wiki, you can find info about the disk resource widget here: https://github.com/benphelps/homepage/wiki/Information-Widgets#resources

[Smiggel]

Doesn’t say how to mount the drive/folder using the stack in docker.

[ShlomiPorush]

You need to mount the remote drive on the host server and then add it to homepage container

Add your folder mount to docker-compose.yml
For example

    volumes:
      - /mnt/media1:/mnt/media1:ro
      - /mnt/media2:/mnt/media2:ro

And in widgets.yaml

- resources:
    label: Media1
    disk: /mnt/media1

- resources:
    label: Media2
    disk: /mnt/media2

[Smiggel]

Hmm ok. I will give it a try. Didn’t work for me before. Thanks.

[Smiggel]

You need to mount the remote drive on the host server and then add it to homepage container

Add your folder mount to docker-compose.yml For example

    volumes:
      - /mnt/media1:/mnt/media1:ro
      - /mnt/media2:/mnt/media2:ro

And in widgets.yaml

- resources:
    label: Media1
    disk: /mnt/media1

- resources:
    label: Media2
    disk: /mnt/media2

Thanks. Got it to work now. :-)

[JazzFisch]

Thanks for all of the great suggestions everyone. I'm closing.

[MortRainey]

And how do i get CPU and Memory from host. I have running hompage inside a lxc container on proxmox.

[tautomer]

And how do i get CPU and Memory from host. I have running hompage inside a lxc container on proxmox.

I more or less got this worked in a really ugly way.
First, you need mount /proc to your lxc, like what is suggested in the post below
https://www.linuxquestions.org/questions/linux-server-73/using-web-monitor-within-lxc-to-monitor-core-server-4175646014/
Unfortunately, unlike netdata, I don't think you can customize the data source in homepage. They are hardcoded, like

 cpuinfo = fs.readFileSync('/proc/cpuinfo', { encoding: 'utf8' }).toString().split('\n');

So I directly mounted the host's /proc to the lxc's /proc.
Then another issue kicked in https://github.com/lxc/lxd/issues/2238. Directly mounting /proc to the lxc will make it unbootable.
At the end, my whole workaround is

# mount /proc to /mnt/proc
mount -t proc proc /mnt/proc

then modify the lxc settings to mount /mnt/proc

lxc.mount.entry: /mnt/proc proc none bind,create=dir

CPU, RAM, and up time are all from the host.

I'm not sure if we mount /proc to /host/proc and globally replace all occurrences of "/proc" to "/host/proc" in homepage will work or not. Maybe we should open a new feature request.

[swarshah]

And how do i get CPU and Memory from host. I have running hompage inside a lxc container on proxmox.

Better approach here would be to use glances https://gethomepage.dev/v0.7.0/widgets/info/glances/

[crispybegs]

You need to mount the remote drive on the host server

sorry for the noob question, but can you help with this bit?
I have two separate headless servers, with Homepage running in docker / portainer on one of them.

How can I mount the drives from the non-homepage server to the homepage server, with CLI or something? No UI / sceren access.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.