---
title: Awesome selfhosted is selfTOASTED? Help is here!
description: When there's something strange, and it don't look good, who you gonna call? Discord / forum / one-on-on support, that's who!
---
# Support

!!! note "Excuse me... waiter, there's a bug in this recipe!"

How do you get support for these receipes? There are several options...

## Discord: Where the cool kids are

All the cool kids are hanging out in the [Discord server](/community/discord/).

!!! question "Eh? What's a Discord? Get off my lawn, young whippersnappers!!"

Yeah, I know. I also thought Discord was just for the gamer kids, but it turns out it's great for a geeky community. Why? [Let me elucidate ya.][2]..

1. Native markdown for code blocks
2. Drag-drop screenshots
3. Costs nothing, no ads
4. Mobile notifications are reliable, individual channels mutable, etc

## Discourse: Long-live discussion!

For community support and engagement, we have a [Discourse forum][3]. Using this as the primary means of topical discussions makes it easy to share recipes / experiences with future geeks.

## Discuss a recipe

Every recipe includes a section at the end for comments.

If you have a comment / question about a specific recipe, navigate to the recipe, scroll to the bottom, and add your comment. You'll be sent to the [kitchen][4] to post the actual comment, but it'll be visible beneath the recipe _and_ at the kitchen. (_To post, you'll need to sign in using OAuth from Discord, github, google, etc, or create a new account_)

## Request a recipe

I'd love to hear your ideas for more recipes. To request/suggest a recipe, create a new post in the [kitchen][5] with the details.

## Contribute a recipe

The only thing I love more than recipe ideas is recipe contributions! See details on contributing a recipe [here](/community/contribute/)

## Spit out a bug

Found a bug in your soup? Tell the chef by either:

1. Commenting on the recipe (see above), or
2. Submitting an issue against the github [repo][6]

## Tip the chef

### [Sponsor][7] / [Patreonize][8] me 💰

The best way to support this work is to become a [Sponsor][11] (_GitHub_) or a [Patron][10] (_Patreon_). Sponsors get:

* warm fuzzies,
* access to the pre-mix repo,
* an anonymous plug you can pull at any time,
* and a bunch more loot based on tier

.. and I get some pocket money every month to buy wine, cheese, and cryptocurrency! 🍷 💰

Impulsively **[click here (NOW quick do it!)][11]** to sponsor me, or instead thoughtfully and analytically review my GitHub profile **[here][12]** and make up your own mind.

### Buy me a coffee ☕️

A sponsorship is too much commitment, and a book is TL;DR? Hit me up with a [one-time caffine shot](https://www.buymeacoffee.com/funkypenguin)!

### Engage me 🏢

--8<-- "work-with-me.md"

[1]: http://chat.funkypenguin.co.nz
[2]: https://www.youtube.com/watch?v=1qHoSWxVqtE
[3]: https://forum.funkypenguin.co.nz/
[4]: https://forum.funkypenguin.co.nz/
[5]: https://forum.funkypenguin.co.nz/
[6]: https://github.com/funkypenguin/geek-cookbook/issues
[7]: https://github.com/sponsors/funkypenguin
[8]: https://www.patreon.com/funkypenguin
[10]: https://www.patreon.com/bePatron?u=6982506
[11]: https://github.com/sponsors/funkypenguin
[12]: https://github.com/funkypenguin
[13]: https://www.youracclaim.com/badges/a0c4a196-55ab-4472-b46b-b610b44dc00f/public_url
[14]: https://www.funkypenguin.co.nz


--8<-- "common-links.md"