argus-htmx-frontend 0.17

HTTP Frontend as a django app for argus-server using HTMx

Experimental frontend for argus-server as a django app.

Will possibly cease to exist as a separate app if the experiment is deemed successful.

See argus-server for more about argus.

Imports django-htmx. See the documentation for django-htmx for details.

How to play

Install

To make sure you do not accidentally work on an old argus-server, do the following:

1. Use/make a venv, for instance: create a new one with python -m venv argus-htmx

2. Check out argus-server code

3. Install argus-server dynamically into the venv: pip install -e .

4. Check out this repo

5. Install this app dynamically into the venv: pip install -e .

It is now safe to remove argus-server from the venv if you feel like it.

Configure

Do this in your workdir, which could be the checked out argus-server repo.

This assumes that you have a local settings file (we recommend calling it “localsettings.py” since that is hidden by .gitignore) as a sibling of src/.

At the top of this local settings file, copy the contents of argus.htmx.settings. This will base the settings-file on argus.site.settings.backend and automatically use argus.site.utils.update_settings with argus_htmx.app_config.APP_SETTINGS to set/overwrite some settings and mutate others. Note the usage of globals(); due to this, inheriting from argus.htmx.settings will probably not work as expected.

While developing you will probably prefer to swap out argus.site.settings.backend with argus.site.settings.dev, as the former is almost production-ready while the latter is tuned for development and depends on the optional dependencies you can install via pip install argus-server[dev].

The argus.site.utils.update_settings function will add or change the settings

• INSTALLED_APPS

• LOGIN_REDIRECT_URL

• LOGIN_URL

• LOGOUT_REDIRECT_URL

• LOGOUT_URL

• MIDDLEWARE

• PUBLIC_URLS

• ROOT_URLCONF

• TEMPLATES

See argus_htmx.appconfig._app_settings for what is being set. The management command printsettings (which depends on the app django-extensions, a dev-dependency) will print out the complete settings used.

Customizing

If you add more pages and endpoints you will have to write your own root urls.py and set ROOT_URLCONF appropriately.

If you have some other apps you want installed and configured, you could either add the necessary settings to your localsettings.py or use the extra-apps machinery. The later is especially useful during the development phase when you haven’t settled on which apps to use yet.

With extra-apps machinery

You make a JSON-file which is read into your settings via one of two environment variables.

In order to add apps and settings that extend argus-server and this app you use the environment variable ARGUS_EXTRA_APPS:

export ARGUS_EXTRA_APPS=`cat extra.json`

If you want to override existing apps the environment variable to use is ARGUS_OVERRIDING_APPS:

export ARGUS_OVERRIDING_APPS=`cat overriding.json`

Have a look at the contents of argus_htmx.appconfig._app_settings for an example of what you can set this way.

You can merge your urlpatterns with the apps’ urlpatterns via the argus.site.utils.get_urlpatterns function, see argus.htmx.urls for an example.

Optional authentication backend settings

If using django.contrib.auth.backends.RemoteUserBackend (which depends on the middleware django.contrib.auth.middleware.RemoteUserMiddleware) there’s an optional setting ARGUS_REMOTE_USER_METHOD_NAME to choose what to show on the button.

If using social_core.backends.open_id_connect.OpenIdConnectAuth there’s an optional setting ARGUS_OIDC_METHOD_NAME to choose what to show on the button.

Both can be set via environment variables.

Update

On every new version, reinstall the dependencies since there might be new ones.

Themes and styling

To try out daisyUI themes use the context processor argus_htmx.context_processor.theme_via_session instead of argus_htmx.context_processor.theme_via_GET.

Default included themes are: light, dark and argus.

This project supports Tailwind CSS utility classes and daisyUI components for styling. Below is an overview of the stack, installation and build instructions, and configuration details for themes and styles.

Overview

• Tailwind CSS: A utility-first CSS framework for rapidly building custom user interfaces.

• daisyUI: A component library for Tailwind CSS that provides a set of ready-to-use components as well as color themes.

Installation and build instructions

Recommended but open for tweaks and adaptations steps:

1. Get Tailwind standalone CLI bundled with daisyUI from https://github.com/dobicinaitis/tailwind-cli-extra

   Most linux:

   $ curl -sL https://github.com/dobicinaitis/tailwind-cli-extra/releases/latest/download/tailwindcss-extra-linux-x64 -o /tmp/tailwindcss
   $ chmod +x /tmp/tailwindcss

   For other OSes see https://github.com/dobicinaitis/tailwind-cli-extra/releases/latest/ and update the bit after download/ accordingly.

   Optionally you can compile tailwind+daisyUI standalone cli bundle yourself as described here: https://github.com/tailwindlabs/tailwindcss/discussions/12294#discussioncomment-8268378.

2. (Linux/OsX) Move the tailwindcss file to your $PATH, for instance to ~/bin/ or .local/bin.

3. Go to the repo directory (parent of src/)

4. Build main stylesheet file using tailwindcss executable from step 1 and pointing to the included config file:

   Manually:

   tailwindcss -c src/argus_htmx/tailwindtheme/tailwind.config.js -i src/argus_htmx/tailwindtheme/styles.css --output src/argus_htmx/static/styles.css

   Running with the --watch flag for automatic update on change seems error-prone so we’ve made it very easy to run the command, with make or tox:

   make tailwind
   tox -e tailwind

   Either will rebuild the styles for you.

Customization

How to customize the look:

• Override Argus’ Tailwind CSS theme defaults and/or choose which daisyUI color themes to include. You can do so by updating the default TAILWIND_THEME_OVERRIDE and DAISYUI_THEMES values respectively before running a tailwind_config management command:

  Via environment variables, for example:

  TAILWIND_THEME_OVERRIDE = '
    {
      "borderWidth": {
        "DEFAULT": "1px"
      },
      "extend": {
        "borderRadius": {
          "4xl": "2rem"
        }
      }
    }
  '
  DAISYUI_THEMES = '
    [
      "light",
      "dark",
      "cyberpunk",
      "dim",
      "autumn",
      { "mytheme": {
          "primary": "#009eb6",
          "primary-content": "#00090c",
          "secondary": "#00ac00",
          "secondary-content": "#000b00",
          "accent": "#ff0000",
          "accent-content": "#160000",
          "neutral": "#262c0e",
          "neutral-content": "#cfd1ca",
          "base-100": "#292129",
          "base-200": "#221b22",
          "base-300": "#1c161c",
          "base-content": "#d0cdd0",
          "info": "#00feff",
          "info-content": "#001616",
          "success": "#b1ea50",
          "success-content": "#0c1302",
          "warning": "#d86d00",
          "warning-content": "#110400",
          "error": "#ff6280",
          "error-content": "#160306"
          }
      }
    ]
  '

  Or by providing corresponding values in your local settings that star-imports from an argus-server settings file:

  TAILWIND_THEME_OVERRIDE = {...}
  DAISYUI_THEMES = [...]

  Some links that may be relevant for the customization values mentioned above:

  • daisyUI themes

  • list of daisyUI color names

  • Tailwind CSS theme customization

• Override the default main stylesheet path by setting ARGUS_STYLESHEET_PATH in the environment. The path is under STATIC_URL. This depends on the context processor argus_htmx.context_processors.path_to_stylesheet.

• Include additional styles/stylesheets using the head block in your templates.

• Generate a Tailwind config file by running the tailwind_config management command. By default the generated file will be based on src/argus_htmx/tailwindtheme/tailwind.config.template.js and expected values will be injected with reasonable defaults.

UI Settings

Incident table column customization

You can customize which columns are shown in the incidents listing table by overriding the INCIDENT_TABLE_COLUMNS setting. This setting takes a list of str or argus_htmx.incidents.customization.IncidentTableColumn instances. when given a str, this key must be available in the argus_htmx.incidents.customization.BUILTIN_COLUMNS dictionary. For example:

from argus_htmx.incidents.customization import BUILTIN_COLUMNS, IncidentTableColumn

INCIDENT_TABLE_COLUMNS = [
    "id",
    "start_time",
    BUILTIN_COLUMNS["description"], # equivalent to just "description"
    IncidentTableColumn( # a new column definition
        name="name",
        label="Custom"
        cell_template="/path/to/template.html"
        context={
            "additional": "value"
        }
    ),

]

For inbuilt support for other types of columns see the howtos in the local docs.

Custom widget

Argus supports showing an extra widget next to the menubar in the incidents listing. This box can take the width of 1/3 of the window. You can add the widget by creating a context processor that injects an incidents_extra_widget variable that points to an html template:

def extra_widget(request):
    return {
        "incidents_extra_widget": "path/to/_extra_widget.html",
    }

note Don’t forget to include the context processor in your settings

You could then create path/to/_extra_widget.html as following:

<div id="service-status" class="border border-primary rounded-2xl h-full p-2">
  My custom widget
</div>

Page size

By default, incidents are shown with a page size of 10 (ie. 10 rows at a time), and the user can select a different page size from [10, 20, 50, 100]. It possible to override these settings by setting the ARGUS_INCIDENTS_DEFAULT_PAGE_SIZE and ARGUS_INCIDENTS_PAGE_SIZES setting respectively.