Make asset busting depend on deployment environment
default tip
3 weeks ago, Jason Allan
Make asset busting depend on deployment environment

At the moment CSS and JS resources have a cache busting tag at the end of their href/src to force a reload when re-rendered. This is deependant on an unused setting, and is present in prod as well, this is really only a feature for development. So, it's been a PITA when diffing outputs

Testing Done:
I've run the `hugo` and `hugo serve` commands with deployment env between prod and dev, and behaviour is as expected

Reviewed at
title: Sametime
date: 2019-08-07T22:48:49.000Z
replaces: []
weight: 50
lastmod: 2019-08-22T02:35:41.000Z
### Are there any public Sametime servers?
Apart from a demonstration server hosted by Lotus/IBM, no. This protocol is
designed to connect to a Lotus/IBM Sametime server running on a corporate LAN.
### Why doesn't Sametime appear in the protocols list?
Sametime support in Pidgin depends on a separate library called Meanwhile. You
will need to install the Meanwhile library and the `libpurple-meanwhile` (or
similar, depending on distribution) package to enable Sametime support. If you
are building Pidgin from source, then the Sametime plugin will be built
automatically if you have the development headers for Meanwhile installed.
### Why do I get the error "Not Authorized" when connecting?
The Sametime server to which you're attempting to connect has been configured
with a whitelist of acceptable clients. This error indicates that the client ID
used by Pidgin (`0x1700`) is apparently not in that whitelist, so the server
denies your login. You can cause Pidgin to masquerade as the default Sametime
Connect client by setting the "Hide client identity" option in your account