Feat/s3 file browser v1

[dklOrdix]

Closes #129

[Bohreromir]

@F3l1x1vo Whoops my bad. I meant using ctrl+v into the field for the new file name

[F3l1x1vo]

I meant using ctrl+v into the field for the new file name

There's a conflict there with the regular pasting of text. If the user wants to copy and paste a filename he copied from outside the browser for example, a file in the clipboard of the storage browser would be pasted into that field instead of his text. This pasting of filenames by the clipboard is a very niche and weird interaction that I would suggest to leave out.

[Bohreromir]

some more

[F3l1x1vo]

@Bohreromir I've added rar support via node-unrar-js in 68cac8e. Please check it out and tell me if it's acceptable to Stackable.

[Bohreromir]

Closed and reopened to fix github action bug :')

[Bohreromir]

Unfortunately the dev setup no longer works for me:

cockpit on  feat/s3-file-browser-v1 [$+] via  v24.19.0 via ❄️  impure (nix-shell-env) took 47s 
❯ npm run dev

> @stackable/stackable-cockpit@0.0.1 dev
> vite dev --host

ℹ [paraglide-js] Compilation skipped — inputs unchanged (locale-modules)                              

  VITE v7.3.6  ready in 1048 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://192.168.178.41:5173/
  ➜  Network: http://100.81.235.8:5173/
  ➜  Network: http://172.19.0.1:5173/
  ➜  Network: http://172.18.0.1:5173/
  ➜  press h + enter to show help
[12:12:58.859] WARN: DATABASE_PASSWORD not set, using default development password
    service: "stackable-cockpit"
    module: "database"
[12:12:58.926] INFO: Running database migrations...
    service: "stackable-cockpit"
    module: "migrations"
[12:12:58.933] ERROR: Database migrations failed
    service: "stackable-cockpit"
    module: "migrations"
    error: {
      "query": "CREATE SCHEMA IF NOT EXISTS \"drizzle\"",
      "params": [],
      "cause": {
        "code": "ECONNREFUSED"
      }
    }
Error: Database migrations failed
    at Object.init (/home/jfleck/dev/cockpit/src/hooks.server.ts:126:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async eval (/home/jfleck/dev/cockpit/node_modules/@sveltejs/kit/src/runtime/server/index.js:142:6)
    at async Server.init (/home/jfleck/dev/cockpit/node_modules/@sveltejs/kit/src/runtime/server/index.js:108:3)
    at async file:///home/jfleck/dev/cockpit/node_modules/@sveltejs/kit/src/exports/vite/dev/index.js:526:5

[F3l1x1vo]

Unfortunately the dev setup no longer works for me

@Bohreromir I've deployed a fix in 7756742 that hopefully works for you. I didn't have an issue with the setup script but I have had the same error when running e2e tests from npx playwright test instead of using npm run test:e2e.