| blueprint: | |
| name: Appliance has finished | |
| description: Do something when an appliance (like a washing machine or dishwasher) | |
| has finished as detected by a power sensor. | |
| domain: automation | |
| input: | |
| power_sensor: | |
| name: Power Sensor | |
| description: Power sensor entity (e.g. from a smart plug device). | |
| selector: |
| import SwiftUI | |
| struct ContentView: View { | |
| var body: some View { | |
| AnimatedBackground().edgesIgnoringSafeArea(.all) | |
| .blur(radius: 50) | |
| } | |
| } | |
| struct AnimatedBackground: View { |
| @main | |
| struct MyApp: App { | |
| enum Sheet { case first, second } | |
| @State var sheet: Sheet? = nil | |
| var body: some Scene { | |
| WindowGroup { | |
| VStack { | |
| Button("First") { sheet = .first } |
| import SwiftUI | |
| struct EnumPicker<T: Hashable & CaseIterable, V: View>: View { | |
| @Binding var selected: T | |
| var title: String? = nil | |
| let mapping: (T) -> V | |
| var body: some View { |
| // | |
| // ContentView.swift | |
| // | |
| // Created by Chris Eidhof on 20.04.20. | |
| // Copyright © 2020 objc.io. All rights reserved. | |
| // | |
| import SwiftUI | |
| import UIKit |
| // | |
| // DarwinNotificationCenter.swift | |
| // | |
| // Copyright © 2017 WeTransfer. All rights reserved. | |
| // | |
| import Foundation | |
| /// A Darwin notification payload. It does not contain any userInfo, a Darwin notification is purely event handling. | |
| public struct DarwinNotification { |
| /** | |
| * MacEditorTextView | |
| * Copyright (c) Thiago Holanda 2020-2021 | |
| * https://bsky.app/profile/tholanda.com | |
| * | |
| * (the twitter account is now deleted, please, do not try to reach me there) | |
| * https://twitter.com/tholanda | |
| * | |
| * MIT license | |
| */ |
Problem: You want to maintain multiple different versions of python and keep packages separated based on projects that you're working on.
Solution: Use the pyenv, virtualenv tools along with the pyenv-virutalenv plugin to manage multiple versions of python and seamlessly integrate them with your projects' virtual environments.
Last updated March 13, 2024
This Gist explains how to sign commits using gpg in a step-by-step fashion. Previously, krypt.co was heavily mentioned, but I've only recently learned they were acquired by Akamai and no longer update their previous free products. Those mentions have been removed.
Additionally, 1Password now supports signing Git commits with SSH keys and makes it pretty easy-plus you can easily configure Git Tower to use it for both signing and ssh.
For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing your commits with GPG.
This gist is now deprecated in favor of our official documentation: https://documentation.portainer.io/api/api-examples/ which contains up to date examples!
Please refer to the link above to get access to our updated API documentation and examples.