As configured in my dotfiles.
start new:
tmux
start new with session name:
As configured in my dotfiles.
start new:
tmux
start new with session name:
<?xml version="1.0" encoding="UTF-8"?> | |
<persistence xmlns="http://java.sun.com/xml/ns/persistence" | |
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence | |
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" | |
version="1.0"> | |
<!-- derby --> |
Hello again, hopefully after reading this you'll be able to understand how RUCKUS ZoneDirector does certain things under the hood. I will cover 4 things in this little Gist, first of all I will show you how to authenticate using PowerShell and keep the session stored. As a base for this guide I will be using this writeup so be sure to read that for the details I will surely miss out on mentioning. This is for a basic SysAdmin who wants to let users do certain things with ZoneDirector without having to give any control of the actual system itself.
Since in my enviroment we use a valid SSL certificate you may or may not need to add this simple hack to the top of your PowerShell.
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
blueprint: | |
name: Yet Another Motion Automation | |
description: > | |
# YAMA V10 | |
Turn on lights or scenes when motion is detected. | |
Four different scenes can be defined depending on time of day. | |