-
Ensure a docker-compose.yml file exists inside a
codimd
directory. -
Put the restore.sh script near it.
-
Follow the script below:
.snowflakes-container { | |
overflow: hidden; | |
filter: drop-shadow(0 0 10px #65b2e4); | |
position: fixed; | |
top: 0; | |
left: 0; | |
right: 0; | |
bottom: 0 | |
} |
.lightrope { | |
text-align: center; | |
white-space: nowrap; | |
overflow: hidden; | |
position: absolute; | |
z-index: 9999; | |
margin: -17px 0 0 0; | |
padding: 0; | |
pointer-events: none; | |
width: 100%; |
# What is This Script? | |
# This script allows you to broadcast your AzuraCast radio signal to a remote video stream, using a | |
# static video file that loops in the background and dynamically writing the currently playing track | |
# on top of that video file. | |
# | |
# This script replaces the previous "radio-video-stream" project, allowing you to manage files directly from | |
# within AzuraCast and not requiring any changes to your Docker configuration at all. | |
# | |
# To use this script, you must be running at least AzuraCast 0.19.0 or a later Rolling Release version. | |
# |
devices: ({ | |
name: "MX Anywhere 3"; | |
hiresscroll: { | |
hires: true; | |
invert: false; | |
target: false; | |
up: { | |
mode: "Axis"; | |
axis: "REL_WHEEL_HI_RES"; |
Alle Daten die man benötigt sind schon im Station-Response drinnen. In diesem Beispiel nehmen wir einfach die Daten daraus und wiederholen den Aufruf alle 1,5 Sekunden um aktuell zu bleiben.
Das Beispiel besteht aus zwei Dateien. Einem HTML-File namens index.html
. Dieses definiert nur eine sehr grobe Grundstruktur in der die Daten dargestellt werden. Das zweite File heißt azura_beispiel.js
und definiert die Logik, die die Daten abruft und darstellt.
#!/bin/sh | |
# Nagios shoutcast plug-in | |
# By Juliano Jeziorny ([email protected]) | |
# Rev 0.1 | |
# 23/11/2010 | |
# ********************************************************* | |
# Modified and adapted for Shoutcast 2 to parse xml stats | |
# and detect unconnected source | |
# Rev 0.2 by Keijo D. Putt | |
# 07-Dec-2017 |
#include "znc/main.h" | |
#include "znc/User.h" | |
#include "znc/Nick.h" | |
#include "znc/Modules.h" | |
#include "znc/Chan.h" | |
#include "znc/IRCNetwork.h" | |
#include <string.h> | |
using std::pair; | |
using std::map; |
This is a widget for the Smashing dashboard. It displays quite a bit of statistics about your Bacula backup server environment.
It should be opbvious, but you will need a fully functional Bacula (community or enterprise edition) installation. This widget makes use of the Bacula command line tool called bconsole to query the Director for information, then sends the data to the Smashing server via curl.
Copy the smashing-BaculaStatus.sh bash shell script to any directory you like. It may be somewhere on the smashing server, on the Bacula Director, or any machine where cron is available. Near the top of this file, edit the variables to match your system. You will need to create a bconsole-smashing.conf file, and the information (password etc) in this file will need to match a console section in the Director's "bacula-dir
#!/bin/bash | |
#=============================================================================== | |
# HEADER | |
#============================================================================== | |
# IMPLEMENTATION | |
#% name bash_template | |
#% title Bash Shell Template | |
#% version 0.0.1 | |
#% checksum 5926ed74eb9baf0dc74b08e2e9be26a0 | |
#% author Matthew Myers |