agentbbs/internal/files
Anthony Ettinger f2bcb7e063 files: /me and /public are two separate per-user areas
Per feedback: /me is PRIVATE and the public folder must be its own
top-level area, not nested under /me.

- A member now has two sibling areas over SFTP: /me (private,
  <root>/files/users/<name>) and /public (their own public files,
  <root>/files/public/<name>), served anonymously at ~<name>/public.
- Drop the global shared /public web route and the /me/public nesting.
  The anon surface only exposes ~name/public; /me has no anon route.
- Both owned areas count toward the quota gauge.
- Index publish hint, docs, and setup.sh updated to scp :/public/.

files.<host> stays a file server; member sites remain on the BBS.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-26 01:36:43 +00:00
..
admin.go feat(files): SFTP member storage — private workspaces + shared public area + mgmt TUI 2026-06-23 09:35:04 +00:00
backend.go files: /me and /public are two separate per-user areas 2026-06-26 01:36:43 +00:00
e2e_test.go files: per-user public at ~name/public; home = member directory 2026-06-26 01:21:00 +00:00
files_test.go files: /me and /public are two separate per-user areas 2026-06-26 01:36:43 +00:00
fs.go files: /me and /public are two separate per-user areas 2026-06-26 01:36:43 +00:00
server.go feat(files): SFTP member storage — private workspaces + shared public area + mgmt TUI 2026-06-23 09:35:04 +00:00
tui.go feat(files): SFTP member storage — private workspaces + shared public area + mgmt TUI 2026-06-23 09:35:04 +00:00
web.go files: /me and /public are two separate per-user areas 2026-06-26 01:36:43 +00:00
web_test.go files: /me and /public are two separate per-user areas 2026-06-26 01:36:43 +00:00