@gromek1243 feel free to code an emulator/distro yourself
I wrote the documentation that you don't read.
Posts made by herb_fargus
RE: Lightning bolt problem
I was using a cable and USB adapter the person on eBay supplied
Cheap Chinese eBay knickknackery strikes again.
I'd recommend reputable sellers for pi hardware (haven't had too much luck with eBay so I've stopped buying from there)
RE: Emulator not appearing in Retropie (ROMS added, Bios added, cfg file checked, etc)
Pre-made. Bought off eBay already set up (minus ROMS and two emulators I'm trying to install
They sold you retropie illegally https://retropie.org.uk/about/legal/ . You'll have to ask the seller for support as we have no idea what they have done to it.
RE: Operation Make the Wiki Pretty!
@detron I had considered using readthedocs as it has options for html/PDF/epub export along with versioning but I didn't want to go through the hassle of converting markdown to restructured text. It would have been prohibitive especially if we want the community to continue to contribute to the wiki. Markdown is much simpler.
The process for creating the static pages is relatively simple through some parsing. Basically we clone the GitHub wiki repo, parse the markdown to HTML and generate the static pages through makedocs with minor configs/css etc.
@BuZz actually created a useful module that can be run manually that will generate the docs locally.
sudo ~/RetroPie-Setup/retropie_packages.sh wikidocs depends
sudo ~/RetroPie-Setup/retropie_packages.sh wikidocs sources
sudo ~/RetroPie-Setup/retropie_packages.sh wikidocs build
sudo ~/RetroPie-Setup/retropie_packages.sh wikidocs install
Should generate a folder of the static pages in
~/RetroPie-Setup/tmp/build/wikidocsI believe ( or something like that, don't have access to my pi to check
The upload function is what we use to push updates to our server but requires an ssh key, a server side script runs the builds automagically though so we don't have to push updates manually.
RE: let's improve ES docs
@meleu if we were to do it proper we'd have a source like a branch with assets on this repo
But the docs change all the time and I didn't want to keep swapping out images. Plus I don't really see GitHub as the best option for hosting images but I digress. Functions for now as is, retropie is a lot to manage as it is, and docs are almost a separate project on their own. Anyways I appreciate your help with this as I've fallen out of form with docs/retropie with the unfortunate responsibilities of real life.