Fixed NoAuth option

[AJolly]

✍️ Description

the previous method created a user ID with a password of 1 which did not meet complexity requirements, this consolidates the config initialization and fixes the no-auth option.

🔗 Related PR / Issue

Link: #

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.
  Has the same previous hard coded secrets.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

[MickLesk]

Doesnt work.

/usr/local/community-scripts/filebrowser.db does not exist. Please run 'filebrowser config init' first.

You have removed important commands, which means that the database is not initialized correctly. I built the commands this way because it worked without any problems.

[AJolly]

huh. I'll go retest. Creating the user with the password of 1 did not work (when i tried the command directly), so no-auth wouldnt work for me.
Also very weird - the setup script means filebrowser conf show doesnt work.