maran/dnseth 20

DNS Server demo with Ethereum as backend

maran/electrum-winbuild 4

Create Electrum windows builds on Linux using Docker.

maran/electrum-sync-server 3

Server for the Electrum label sync plugin.

maran/authlogic 2

A clean, simple, and unobtrusive ruby authentication solution.

maran/bort 2

A base rails app featuring: RESTful Authentication, Will Paginate, Rspec & Rspec-rails, Exception Notifier, Asset Packager, Cap Recipe (multi-stage). Put together by Fudge to remove the need for boring project setup.

maran/docker-build-geth 2

Build the Ethereum-cli client Geth using Docker

maran/docker-plex-pass 2

This is a Dockerfile to set up Plex Media Server

maran/electrum 2

Electrum; Bitcoin thin client

maran/ethchain-go 2

Ethereum Go chain package

maran/accountant 1

Personal accountant

issue openedAnalogJ/scrutiny

[FEAT] Grouping disks by host

Describe the solution you'd like I'm debating using Scrutiny to monitor my cluster of bare metal servers. However in this scenario Scrutiny would end up with hundreds of disks to monitor.

For my specific use-case seeing which disk is on which server would be necessary to make sense of it all. Ideally the disks would even be grouped by their hosts. So that you first select a server and then see the disks available in that server and their status. Perhaps an optional screen with all disks with warnings across the cluster could be added too.

I'm not sure if I'm unique with this requirement but so if you need something similar please let me know :)

created time in 21 days

issue commentAnalogJ/scrutiny

[FEAT] Multiple monitored servers/separate collector+webapp server/VMs?

I've done what you outlined this morning on a few test servers in my cluster and it works fine. Just run the correct Docker images as provided in the readme and everything you want works.


comment created time in 21 days

issue commentAnalogJ/scrutiny


Just came in to 👍 some form authentication. I wanted to collect harddisk data over a cluster of servers and even though it's read-only I still feel that my cluster should not be public information. Basic Auth would be fine as a start as it's quite easy to implement and will probably cover most use-cases.


comment created time in 21 days

push eventOlarisTV/olaris-server

Maran Hidskes

commit sha 432918e78a586fd44020dd63e9029b5548d9f2ca

Update Rclone support

view details

push time in 2 months

push eventmaran/ransack-mongoid


commit sha a56a8ac72be816a34e6f4d3cbb3c583908d0bca2

incremented versions for gems to rails 6 ruby 2.7.0 and mongo 7

view details


commit sha b7f68881081731afdfaa010499d06adc93d17d71

bumped version from 0.1.0 to 0.1.1

view details

Ondrej Huta

commit sha 3d9b1b579c6a96ab9d66d751e6f9f5edd460927a

Add ransack node sort method

view details


commit sha 48a69ef5a5d58d40eeedf4903c3424fe0fa801ac

Merge pull request #1 from jesusalc/rails-6-mongoid-7-ruby-2-7-0 Rails 6 mongoid 7 ruby 2 7 0

view details

Ondrej Huta

commit sha 99810e0fbf599c09cf970ef0549a5e725e26b5ef

Fix visitor, query

view details

Maran Hidskes

commit sha 0862c970eac8561316abd76f6a3c8b76fb0d0be0

update lock

view details

push time in 2 months