pidgin/nest

Make asset busting depend on deployment environment
default tip
3 weeks ago, Jason Allan
837d728b48d1
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 https://reviews.imfreedom.org/r/145/
---
title: Community
date: 2019-05-19T17:51:27.000Z
anchor: community
weight: 100
replaces:
- developer.pidgin.im/wiki/PidginCommunity
lastmod: 2020-01-14T05:00:21.000Z
---
Pidgin is a huge project with a community that helps to provide support. We
have a number of ways you can get in touch with us.
## E-mail
The Pidgin team can be reached via mailing lists for support and development
information.
- [support@pidgin.im](mailto:support@pidgin.im) ([List Info](https://lists.pidgin.im/listinfo/support)) ([List Archive](https://lists.pidgin.im/pipermail/support/))
- [devel@pidgin.im](mailto:devel@pidgin.im) ([List Info](https://lists.pidgin.im/listinfo/devel)) ([List Archive](https://lists.pidgin.im/pipermail/devel/))
- We offer a few other mailing lists. [See the full list.](https://lists.pidgin.im/listinfo)
## Chat
If you prefer chat-based contact, the Pidgin community has two primary chat
resources:
- `#pidgin` on `irc.freenode.net` on IRC
- `devel@conference.pidgin.im`, a Jabber/XMPP MUC (Multi-User Chat)
## Helping
We often get people asking how they can help. Take a look at the
[Contributing](/development/contributing) page for suggestions! There are lots of things to
do for people, and a lot of them don't even involve the source code!