Hi Selfhosting community.

Was looking for PaperCut alternatives that are self-hostable and preferably open-source. I came across this software: SavaPage. It looks really great, loads of features that ticks many of the boxes I need it for. I want to implement this at our offices. Wondering if anyone here has any experience with this, and if you might be willing to share said experience?

TIA.

cross-posted from: https://lemmy.world/post/26112762

Hi all

I have been searching high and low but I think my search game is too weak. I am looking for a tool (similar to Uptime Kuma) that can monitor multiple systems via their own APIs, to centralise the status of these devices. Ex:

a) I have a sensor system that monitors a whole bunch of sensors across multiple locations. This system has an API that uses a secret key + api key for auth, and I can get the status of the sensor via the api. The idea is that the central dashboard shows the status, if offline, the control room personnel can log into the sensors system itself and determine root cause.

b) I also have a system to which a whole bunch of A/V equipment is connected, and via it's API I am able to view the status of multiple devices on the A/V equipment network. I want to also see on the status of these devices on my central monitoring system.

I don't care about doing root cause analysis via the central monitoring system, I just want the statuses which can action a person to check via the control system of that particular service.

All my searches come back with hits of systems that can monitor whether my APIs are up and running, but that is not what I want. Does anyone have any ideas? Preferably opensource, but definitely self-hosted/on-prem hosting. TIA

Edit: I solved it using Uptime Kuma, and the HTTP(s) JSON Query monitor. Thanks all for the inputs.

Hi all

I have been searching high and low but I think my search game is too weak. I am looking for a tool (similar to Uptime Kuma) that can monitor multiple systems via their own APIs, to centralise the status of these devices. Ex:

a) I have a sensor system that monitors a whole bunch of sensors across multiple locations. This system has an API that uses a secret key + api key for auth, and I can get the status of the sensor via the api. The idea is that the central dashboard shows the status, if offline, the control room personnel can log into the sensors system itself and determine root cause.

b) I also have a system to which a whole bunch of A/V equipment is connected, and via it's API I am able to view the status of multiple devices on the A/V equipment network. I want to also see on the status of these devices on my central monitoring system.

I don't care about doing root cause analysis via the central monitoring system, I just want the statuses which can action a person to check via the control system of that particular service.

All my searches come back with hits of systems that can monitor whether my APIs are up and running, but that is not what I want. Does anyone have any ideas? Preferably opensource, but definitely self-hosted/on-prem hosting. TIA

cross-posted from: https://lemmy.world/post/23009603

This is horrifying. But, also sort of expected it. Link to the full research paper:

Full pdf

Sorry I don't have an english version of this article, this is the best source I could find for it.

https://www-heise-de.translate.goog/news/Microsoft-krallt-sich-Zugangsdaten-Achtung-vorm-neuen-Outlook-9357691.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=de

Hi everyone

I have read through the documentation now several times, and I just want to soundboard something with someone. Regarding the environments we can set up. Is this meant for example as a production cluster and a dev cluster? And if so, is it possible to put a docker swarm cluster in there? I don't see how gitlab will 'know' how to deploy an application to docker swarm? What am I missing? Or am I better off just deploying "manually" via the CI/CD pipeline like I am doing now?

TIA

Hi community

I have a pipeline where a stack (service) is deployed to my docker swarm. I want to use $CI_PROJECT_NAME in my docker service definition file to define the docker service name. But it seems the variable is not being expanded, or something else is wrong. I need to have a generic yml so I can distribute this to all devs and they don't have to change anything.

Example of what I am trying to achieve:

version: '3.9'
services:
  $CI_PROJECT_NAME:
    image: myregistry/devops1/$CI_PROJECT_NAME/$CI_PROJECT_NAME:latest
    deploy:
      replicas: 3
      endpoint_mode: dnsrr
      update_config:
        parallelism: 1
        delay: 3s
        order: start-first
        failure_action: rollback
        monitor: 1m
      restart_policy:
        max_attempts: 3
      placement:
        max_replicas_per_node: 1
    networks:
      - microservices
    volumes:
      - apache-logs:/var/log/

networks:
  microservices:
    external: true


volumes:
  apache-logs:
    driver: local
    driver_opts:
      o: bind
      device: /mnt/swarm_shared/services/$CI_PROJECT_NAME
      type: none

I know this is not a docker forum, but was thinking the issue is with my pipeline rather than my docker compose file. I would appreciate any help I can get. TIA

EDIT: As per this community post I used a sed replacement command to solve my problem. Ugly, but functional.

Thanks for the input!