docs VS fpm

here's the official guide/documentation: https://docs.libretro.com/

We'll deal with it. Looks like it's just the web host, so not that big of a deal. docs.libretro.com and buildbot.libretro.com should still be fine.

I just PRed a blurb that outlines that process based on your comment. Does this look right to you? https://github.com/libretro/docs/pull/840

So, what have you tried for the cheats? Did you make sure the core you're using is compatible with RetroArch's cheats (you can find this information on the cores' pages at docs.libretro.com)?

Sure. You can send PRs to the docs repo https://github.com/libretro/docs/

A log would tell us more, but did you do any of the required setup for those cores? They need BIOS images to function. See the cores' pages on docs.libretro.com for more details.

Emulation Wiki and Libretro docs.

So starting in August 2017, there was a repository called (https://github.com/libretro/docs/) that I contributed frequently to.

If you ever revisit that decision, check out FPM. It can shave off a few of the rough edges related to packaging: https://github.com/jordansissel/fpm

The easiest way is probably FPM: https://fpm.readthedocs.io/en/latest/

There is definitely a lot more to building a proper package for wider distribution, but there are some great tools out there for folks wanting to get into it that make it more approachable. I've done my fair share with fpm when learning how the proverbial sausage is made.

Check out https://github.com/jordansissel/fpm

I use RedHat based environments for work. I've had good success creating my own yum repo and building RPM packages with Effing package management. FPM can handle packages for most distros so if you want to publish a linux app it is an easy way to provide it in multiple formats.