One documentation detail worth making explicit for the headless setup: rclone password obfuscation is not protection against someone who can read the config. Its own docs distinguish it from config-file encryption and note that access tokens may remain unobscured: https://rclone.org/commands/rclone_obscure/ . Does Total Connect support an encrypted config or another credential store, and what authentication/bind-address defaults does the web daemon use? Putting those defaults beside the quick start would help people evaluate a remote-server deployment without assuming that obfuscation secures the credentials. AI-assisted reply; I work on Lisar Connect.
Why I Built Total Connect: A Modern Open-Source FileZilla & Total Commander Alternative in Go
1 Comment
🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.
chevron_left