DockFlare v2.1: Prepare for Takeoff with the Pre-Flight Wizard!

[ChrispyBacon-dev]

Hello everyone,

I'm excited to announce the release of DockFlare 2.1! My focus has been on simplifying the initial setup process, enhancing security, and making the application easier for everyone to manage.

Major New Features

Onboarding Overhaul: The Pre-Flight Setup Wizard

I've eliminated the need for .env files for new installations! Now, when you set up DockFlare for the first time, you'll be greeted with a one-time, browser-based setup wizard. This new "Pre-Flight Mode" will guide you step-by-step through configuring your Cloudflare credentials and tunnel settings. My goal was to make this initial setup process faster and more intuitive for you.

Here’s a sneak peek at the steps:

1. Cloudflare API Token: Securely enter your Cloudflare API token.
   
2. Tunnel Configuration: Configure your desired tunnel name and other settings.
   
3. Create Your UI Password: Secure your DockFlare UI with a new password.
   
4. Setup Complete: A final confirmation that your setup is complete.
   

Enhanced Security: UI Authentication & Password Management

Security is a top priority. With version 2.1, the DockFlare UI is now fully protected by a login page. I've made sure that all sensitive credentials, including your Cloudflare API token and your new UI password, are stored in a fully encrypted configuration file (dockflare_config.dat) on your persistent volume.

This update also introduces:

• Password Changes: You can now change your password directly from the new "Security" section in the Settings page.
• Secure Password Resets: For improved security, password resets are handled manually. I've provided instructions in the UI on how to reset your password by deleting the configuration files. This ensures only users with filesystem access can perform a reset.

Seamless Migration for Existing Users

Upgrading from an older version? I've got you covered. DockFlare will automatically detect your existing .env file, import your settings, and guide you through a quick process to create a new password for the UI. Your existing tunnel and DNS configurations will be preserved, making the transition as smooth as possible.

Here's how the migration will look:

1. Migration Welcome: You'll be prompted to begin the migration process.
   
2. Create UI Password: Create a new password to secure your DockFlare instance.
3. Migration Complete: A confirmation that your settings have been migrated.

Usability Improvements

I've also made several improvements to the user interface and overall usability:

• Post-Setup Configuration: You can now modify core application settings directly from the UI after the initial setup. A new "General Settings" section allows you to change the Tunnel Name, Primary Zone ID, the list of other DNS zones to scan, and the rule grace period at any time.
• Logout Button: A logout button has been added to the main navigation bar for easy and secure session termination.
• Cleaner UI: The theme selector is now an icon-only button for a more streamlined look.

⚠️ Breaking Changes

• Removal of .env File Support: As part of my move to a more secure and robust configuration system, DockFlare no longer reads its configuration from .env files after the initial migration. All configuration is now managed via the encrypted dockflare_config.dat file and the UI.

How to Upgrade

1. Pull the latest Docker image: docker pull alplat/dockflare:stable
2. Restart your DockFlare container.
3. Open the DockFlare UI in your browser. If you are upgrading, you will be automatically guided through the short migration process to create a password for your new secure login.

I'm really proud of this release and I hope it makes your experience with DockFlare even better. As always, I welcome your feedback and contributions!

Cheers,
Chris

---

This discussion was created from the release DockFlare v2.1: Prepare for Takeoff with the Pre-Flight Wizard!.

[GavIngram]

I'm sad about the removal of .env file support. I very much appreciate configurations that are entirely manageable and deployable from the config files, and can be 'overridden' in the gui, but with an option to revert to the defaults set in the config files - like you have done with the Docker labels.
In terms of security for the API key (and any other sensitive config data), it could be configured as a Docker secret - couldn't it?
Anyone else feel the same way?

Just wanna add - DockFlare is awesome. Thanks @ChrispyBacon-dev !

[ChrispyBacon-dev]

Hey, thanks so much for the feedback and the kind words!

That's a really valid point. I'm a big fan of managing everything from config files myself, so I definitely see where you're coming from. My main reason for moving away from the .env file was security. That Cloudflare API token is super powerful, and I was getting worried about people (myself included!) accidentally committing it to a public repo (eg. forking DockFlare make edit with .env and API token etc...) or just leaving it in plain text.

While Docker Secrets are the gold standard, I wanted to find a solution that was secure by default for everyone, even users who aren't familiar with managing them. The pre-flight onboarding and afterwards encrypted file felt like the best middle ground to make the setup both easy and safe.

It's a tough trade-off, and I really appreciate you sharing your perspective on it. For now, I'm planning to stick with the new UI-driven setup, but your feedback is super valuable.

Thanks again for using DockFlare!

Cheers,
Chris