Comprehensive WebUI #1762
Merged
Comprehensive WebUI #1762
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 30 commits
October 6, 2025 01:24
Added detailed onboarding steps and configuration guidelines for new users of the WebUI, including dataset management and training environment setup.
Updated DeepSpeed integration details in README.
Updated tutorial references and quick start instructions in README.
bghira
removed
the
work-in-progress
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this has been in progress for a few weeks, but already allows end-to-end configuration and training.
validations are a bit weird, there's a bunch of room for improvement, but it's far enough along that it can be used somewhat seriously at this point.
please report any issues you might have.
to get started, you'll have to install this branch by git clone and
pip install -e .or, direct via ssh with git. i'd recommend cloning it.once it's up, you can browse to http://localhost:8001/web
when you get to the interface, assuming it all works, you'll see a couple configuration questions that you'll need to answer about where files should be stored. these configs are stored in
~/.simpletuneron Mac and Linux both, in case you have to remove or manually fix them.if you want to reuse your simpletuner env style configs, move them to a new dir.
config/folder to ~/simpletuner/configoutput/folder to ~/simpletuner/outputIf your old paths were using relative paths like
foo/config.jsonthey'll all be detected just fine in their new location. you'll have to update the paths if you're using absolute locations.it doesn't have any kind of security layer at the moment, but it protects you from at least path traversals. so it's not recommended to run this on a public IP unless you like playing roulette.
errata:
some known bugs exist.
no webUI documentation is written.
the user interface notifications, layout, colour scheme, and timing can be off.
the dataset builder interface has a lot of features but currently, using it kinda sucks.
right now there's no way to reset the onboarding setup config (the one in ~/.simpletuner) so you have to manually edit that, but it's almost never needed.
the main bug currently that you'll encounter is that validation images get incorrectly copied to newer checkpoint folders if you dont' have the step interval lined up perfectly eg 50 steps for checkpointing AND 50 step interval for validating.the other is that the event viewer interface tends to just redraw the entire fkn thing for no reason.the remaining issue blocking merge is simply usability tweaks and documentation.
configuring the model path, flavour, etc
managing checkpoints