Simple HLKY -> Voldemort(Automatic1111) migration

Do you:
-Have hlky running but want to try out the so-called "voldemort" repo with the nice looking UI and extra settings?
-Want to keep using the CMD launchers like a lazy retard?
-Want to keep everything nicely contained within the Miniconda environment you so painstakingly set up by double clicking that cmd?

Follow this guide to fairly quickly use your existing hlky repo and scripts to have access to hlky and automatic1 via cmd files. Not intended to be a nice permanent setup, just enough that it should work fine for a while, by which point there's likely to be a more unified/converged stable repo, maybe even with an easier install process.

1. Get the other webui with "git clone https://github.com/AUTOMATIC1111/stable-diffusion-webui.git". For the location, nest it within your existing stable-diffusion hlky repo; so that alongside your root hlky "webuild.cmd" etc etc you have a new folder probably by default called "stable-diffusion-webui". Probably rename it to "stable-diffusion-voldy" to help your aging brain keep track of what's going on when you inevitably forget what you are doing
2. The two files used to launch hlky webui are whichever cmd file you run (webuildm.cmd or webui.cmd) and "relauncher.py" in /scripts, so you need to make a changed copy of both. make a copy in place of the cmd called "webui_voldy.cmd" or something vaguely similar and do the same for a new "relauncher_voldy.py".
   2a) In the "webui_voldy.cmd" change line 5 and line 10 to point to "relauncher_voldy.py" instead of the original.
   2b) Now in "relauncher_voldy.py" change line 8 to point to "stable-diffusion-voldy/webui.py", i.e. the new code from the new repo you just checked out. (if the path to the new folder looks wrong to you it's because this relauncher script, while being located in /scripts, is run one directory up from that, so probably don't fuck with it)
3. "taming-transformers" needs to be available as well, you'll notice the new repo suggests you check this out two levels up from the voldy checkout which really is a better place to organise it long term, so feel free to, especially since it should allow you to pull voldy updates in future and nothing will break. But if you're lazy, "taming-transformers" is actually bundled with hlky under the "src" folder, so in theory you could nab that one and copy it all the way out to sit alongside your original stable-diffusion folder (i.e. probably not alongside any files). you could also modify a path in a line near the start of your new webui.py from voldy repo, but that'll probably eventually break your future updates and lead to annoying issues, so you can figure out the pitiful remaining bit of work to do that by yourself if for some reason you still want to do it.
4. Now, you should be able to run the new CMD which spins up your conda environment/window and makes the new GUI available, but the final step is to get realesrgan for upscaling. Since you have a nice miniconda environment running everything it would be great to just throw realesr in to that. So we'll slightly edit the environment YAML and get miniconda to update the environment from it
   4a) Open the .cmd file you normally launch with (or the new copy) and check the end of line 4 to make sure you're certain of the name of your miniconda environment you've been using. Probably "ldm" or "ldo". If your environment.yaml doesn't have the same name in it, you'll need to change it now so that it does.
   4b) Open environment.yaml in the stable diffusion base directory and add a line near the bottom, in the "pip" section, copying the format of the other lines, e.g. just below " - facexlib>=0.2.3" add " - realesrgan==0.2.5.0"
   4c) Time to do the update. Open miniconda and navigate to where the environment yaml is. Type "conda activate ldm" (or ldo, or mytestenv, or whatever you had it called), so that the environment your CMDs always activate for you is currently active. then type "conda env update --file environment.yaml"; this will update it with realesrgan
5. Run your new webui_voldy.cmd and it should all work

Now in terms of stuff you have fucked with, you've really just added a couple of scripts (the -voldy.py and -voldy.cmd) which should get ignored by git and should continue to work unless there are large changes. The ONE modification you made is to "environment.yaml" which should be relatively easy to keep an eye on; if you update and there's a conflict, probably just ditch this guide and start over, it will have served its purpose by then