# Generated from ziltoid-1.0.2.gem by gem2rpm -*- rpm-spec -*-
%global gem_name ziltoid

Name: rubygem-%{gem_name}
Version: 1.0.2
Release: 1%{?dist}
Summary: Ziltoid, crontab based monitoring system
License: WTFPL
URL: https://github.com/meuble/ziltoid
Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
BuildRequires: ruby(release)
BuildRequires: rubygems-devel
BuildRequires: ruby
BuildArch: noarch

%description
There are many software applications that aim to watch processes, and keep
them alive and clean. Some of them are well known: god, monit, bluepill.
All have good and bad sides. One of the bad sides is that each alternative is
based on a deamon that computes data and then sleeps for a while. Who is
monitoring this particular deamon ? What if this process suddenly stops ?
Also, you often need root rights to run those tools. On some hosting
environments (mainly in shared hosting), this is an issue.
Ziltoid is an attempt to solve those issues using the crontab system, which
comes with many good sides : it's on every system, it launches a task
periodically then waits for an amount of time, it doesn't need monitoring, it
can send emails to warn of an error and it can run any script.


%package doc
Summary: Documentation for %{name}
Requires: %{name} = %{version}-%{release}
BuildArch: noarch

%description doc
Documentation for %{name}.

%prep
%setup -q -n %{gem_name}-%{version}

%build
# Create the gem as gem install only works on a gem file
gem build ../%{gem_name}-%{version}.gemspec

# %%gem_install compiles any C extensions and installs the gem into ./%%gem_dir
# by default, so that we can move it into the buildroot in %%install
%gem_install

%install
mkdir -p %{buildroot}%{gem_dir}
cp -a .%{gem_dir}/* \
        %{buildroot}%{gem_dir}/



%check
pushd .%{gem_instdir}
# Run the test suite.
popd

%files
%dir %{gem_instdir}
%{gem_libdir}
%exclude %{gem_cache}
%{gem_spec}

%files doc
%doc %{gem_docdir}


%changelog
* Thu Sep 16 2021 mockbuilder - 1.0.2-1
- Initial package