Redesign UI with modern dark theme and improved styling #3
Reference in New Issue
Block a user
Delete Branch "fancy-styling"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
All endpoints remain backward compatible with existing functionality.... but.... the biggest issue is making sure the current tiny sqlite databases don't get overwritten by a checkout or a pull. I think I've solved this by removing the database files from git tracking entirely and adding them to .gitignore. Since SQLite creates these files automatically on first use with CREATE TABLE IF NOT EXISTS, they don't need to be in version control. I've also updated the sanity check to skip permission validation for non-existent database files, so fresh installations will work without issues. When this is merged, git will stop tracking these files but won't delete existing local copies, so production data SHOULD remain safe. (not that it matters)
Before merging, make a copy of the directory just in case, then checkout the local production branch and be sure it works, and just restart the server and it should work. Then idk it's just git hell at that point mayne lmao (I just don't want the biblebot's sequence to be broken, it was a mistake to handle that serverside.)
Okay just some after-thoughts before I turn to my darker projects
Pull request closed