To set cookies on the localhost, either have a self signed cert setup (see refs), or exclude the 'secure', and 'sameSite' directives.
- Be aware of:
- forbidden headers
To set cookies on the localhost, either have a self signed cert setup (see refs), or exclude the 'secure', and 'sameSite' directives.
Despite Digital Transformation and application modernization being well established practices, there are always unforeseen issues the creep up. This exceedingly truncated list of hazards will hopefully help identify some issues early.
💡 This is a companion to -- not a replacement for -- the decadeds of retrospective material that exists on the subject. While it's advisable to engage an outside consultancy if you're unfamiliar with the topic, tackling this list early can offset those costs as their runbook will contain similar content as they assess your application.
Resources
Here are a few vids that give more context to this issue.
| # ---------------------------------------------------------------------- | |
| # File: check_failover_dhcp.ps1 | |
| # Description: NRPE Nagios Check for Windows Server 2012 DHCP Failover Servers | |
| # https://exchange.nagios.org/directory/Plugins/Network-Protocols/DHCP-and-BOOTP/Windows-2012-DHCP-Failover-and-Scope-Health-Check/details | |
| # | |
| # Checks: Failover State | |
| # Failover Mode | |
| # Scope State of Each Scope | |
| # Scope Statistics (PercentInUse) of Each Scope | |
| # |
Project Management can be as simple or as complex as needed. If your project is you and a few highly-aligned folks in the same room then you might be able to make do with a whiteboard and some sticky-notes, but this doesn't scale. There's a lot of expertise involved in taking a project from sticky-notes to a scaled agile enterprise operating model, but the foundations of planning don't change. IE: If you want to dig for treasure, then you should plan to get a shovel to enable your success.
This primer is most useful for founders, PMs, and engineering leaders moving from early execution into repeatable delivery.
Before you jump into executing your vision, start by discovering your minimum viable operating posture (see also the concept of minimum virtuous products), as this dictates a large portion of your overall organizational s
This is my free Evernote alternative.
There are three components of this solution: the note taking app, cloud-sync utility, and the optional cloud storage.
NOTE: If you don't need more than 2GB of cloud storage, you can get away with simply putting the vault in Dropbox and accessing from all your devices. NO NEED FOR SYNCTHING. Otherwise, read on.
Availability is measured in nines. Here's the breakdown:
| Availability % | Downtime/Y | DownTime/Mo | Downtime/w | Downtime/d | Class |
|---|---|---|---|---|---|
| 55.5555555% ("nine fives") | 162.33 d | 13.53 d | 74.92 h | 10.67 h | |
| 90% ("one nine") | 36.53 d | 73.05 h | 16.80 h | 2.40 h | 1 |
| 95% ("one nine five") | 18.26 d | 36.53 h | 8.40 h | 1.20 h | |
| 97% | 10.96 d | 21.92 h | 5.04 h | 43.20 m |
This is not a reprint of the docs, but a collection of tips, tricks, and specific guidance for my own reference, and the development of others.
Build/Install from the Docker Compose Github Releases, as the version available in your operating system's package manager is likely dated, and this component recieves frequent bugfixes.
| #!/usr/bin/env bash | |
| # file_watch.sh | |
| # ------------------------------------------------------------------------------ | |
| # Description: | |
| # Watches a file for changes. | |
| # Includes output on inode changes as that may be desirable in some scenarios. | |
| # NOTE: ... Just use inotifywait. | |
| # | |
| # Usage: | |
| # ./file_watch <path/to/file> |