Package Details: healthchecks 3.7.0-3

Git Clone URL: https://aur.archlinux.org/healthchecks.git (read-only, click to copy)
Package Base: healthchecks
Description: A cron monitoring service with a web-based dashboard, API, and notification integrations.
Upstream URL: https://github.com/healthchecks/healthchecks
Licenses: BSD-3-Clause
Submitter: eta-carinae
Maintainer: eta-carinae
Last Packager: eta-carinae
Votes: 0
Popularity: 0.000000
First Submitted: 2021-05-31 01:53 (UTC)
Last Updated: 2024-11-18 17:06 (UTC)

Latest Comments

MarsSeed commented on 2024-11-17 09:21 (UTC)

Please kindly change the now unsatisfiable optdepend python-apprise to apprise (same package, it just no longer has the virtual provides entry 'python-apprise').

eta-carinae commented on 2024-11-08 17:01 (UTC) (edited on 2024-11-08 17:02 (UTC) by eta-carinae)

I've finally updated Healthchecks to 3.7 now that python-django has been updated in extra. You'll need to stop healthchecks after the update, then manually run:

hc-manage makemigrations --merge

hc-manage makemigrations

hc-manage migrate

before restarting to merge in the database changes.

bjo commented on 2022-07-05 08:43 (UTC) (edited on 2022-07-05 08:45 (UTC) by bjo)

Does not build

    from fido2.ctap2 import AttestedCredentialData
ImportError: cannot import name 'AttestedCredentialData' from 'fido2.ctap2' (/usr/lib/python3.10/site-packages/fido2/ctap2/__init__.py)

It seems to be incompatible with python-fido2 1.0.0.

eta-carinae commented on 2022-03-18 16:47 (UTC)

The upgrade to 2.0.1 introduces a breaking change to the Signal integration. If you're using this, please refer to the healthchecks README to switch to the new integration.

This version also has corrected database settings in local_settings.py.

eta-carinae commented on 2022-03-04 00:25 (UTC)

The build error should be fixed with the update to 1.25.0. If you already have it installed, you'll need to manually run: hc-manage makemigrations to upgrade your database before starting the server again.

I remember looking at the DATABASES setting when I first created the PKGBUILD, and not being sure what to use. I think since I just use sqlite I haven't needed to set it. I'll update the local_settings.py this weekend when I get a chance.

bjo commented on 2022-03-03 21:28 (UTC) (edited on 2022-03-03 21:29 (UTC) by bjo)

Hi, the database settings are wrong. DB gets ignored and could be used as environment.

According to local_settings.py.example, for postgres it should be

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql',
        'NAME': 'your-database-name-here',
        'USER': 'your-database-user-here',
        'PASSWORD': 'your-database-password-here',
        'TEST': {'CHARSET': 'UTF8'}
     }
}

bjo commented on 2022-03-03 19:26 (UTC) (edited on 2022-03-03 19:27 (UTC) by bjo)

Does not build:

CommandError: An error occurred during rendering front/channels.html: [Errno 2] No such file or directory: '/home/bjo/.cache/yay/healthchecks/src/healthchecks-1.24.1/static-collected/CACHE/js/output.b4ba48ed4f66.js'
Compressing... ==> ERROR: A failure occurred in build().