These files allow you to configure Mautic using Nginx.
// Sample config for Alloy that collects metrics, logs, and traces | |
// and forwards them to Grafana Cloud using the Grafana Cloud OTEL | |
// endpoint | |
// | |
// For a full configuration reference, see https://grafana.com/docs/alloy | |
logging { | |
level = "debug" | |
} | |
prometheus.exporter.unix "default" { |
esphome: | |
name: m5stick | |
friendly_name: m5stick | |
esp32: | |
board: m5stick-c | |
framework: | |
type: arduino | |
# Enable logging |
--- | |
apiVersion: apps/v1 | |
kind: Deployment | |
metadata: | |
creationTimestamp: null | |
labels: | |
io.kompose.service: octoprint-server | |
app: octoprint-server | |
name: octoprint-server | |
namespace: default |
apiVersion: apps/v1 | |
kind: Deployment | |
metadata: | |
creationTimestamp: null | |
labels: | |
io.kompose.service: octoprint-server | |
name: octoprint-server | |
namespace: default | |
spec: | |
replicas: 1 |
# Uncomment lines below if you have problems with $PATH | |
#SHELL := /bin/bash | |
#PATH := /usr/local/bin:$(PATH) | |
all: | |
platformio -f run | |
upload: | |
platformio -f run --target upload |
// Be sure to follow the instructions at | |
// https://grafana.com/docs/loki/latest/clients/docker-driver/ | |
// otherwise this will not work! | |
// | |
// Also, remember to remove these comments because JSON doesn't support them! | |
{ | |
"data-root": "/mnt/docker", | |
"metrics-addr" : "10.231.1.21:9323", | |
"experimental" : true, |
Collaborative working can be hard to get right, here's our top 5 tips to encourage a culture of success.
“Collaborative Working is hard“. We’ve heard this from so many of our clients over the years, and often they really struggle with the conflict between [Generalism vs. Specialism][1], and even how to start working in a collaborative manner.
If you go into hospital for a major operation you wouldn’t expect the ward receptionist to administer the anaesthetic, nor would you expect a nurse to carry out the procedure, or the surgeon to perform post-operative care – so why do we expect so many of our software engineers to be “full stack developers”, or our operations teams to have a complete understanding of everything that happens in the process before our product reaches them?
Start by analysing your prod
# Here are some sample commands for checking classics things like | |
# systems and websites | |
# ----------------------------------------------------------------- | |
# | |
# Localhost checks | |
# | |
# ----------------------------------------------------------------- | |
#!/usr/bin/env python | |
import sentry_sdk | |
import json | |
import os | |
import requests | |
import sys | |
from sqlalchemy import create_engine | |
from sqlalchemy.orm import sessionmaker |