File uploads

[gabestein]

Issue(s) Resolved

Oops, forgot to create one.

--> Requires updating core's .env.local file with AWS bucket keys (in our 1Pass).

This adds a (poorly styled!) file uploader using Uppy, as well as some unjournal form enhancements.

There are two outstanding issues I need a little help tracking down:

• somewhere deep in the stack, Zod is complaining about receiving an array in createPub in the form for the file uploads, despite arrays being a valid record (as far as I know?).
• Uppy's UI requires importing CSS from node_modules, which seems impossible to do via Tailwind CSS loaders. So I need a little help on a strategy for that.

Anyway, otherwise it works??

Test Plan

• Create a Pub and invite an evaluator.
• Upload a file. Many files, even.
• Submit and see network response including the pubpub:fileUpload formField value with an array of files including public S3 links!

Screenshots (if applicable)

Optional

Notes/Context/Gotchas

• I could use some double-checking of the permissions settings of the new S3 bucket.
• I had to upgrade our Cloudflare SSL to serve from assets.v7.pubpub.org!
• Right now uses the entire upload URL, but it's being proxied to assets.v7.pubpub.org so we could also parse out the key from the returned URL and use that.
• Right now, all asset links are public, just like in current PubPub assets. Ideally, we'd actually make all asset links private and use another API route to get signed links from core when we need to work with assets. This can be implemented pretty easily in the future.
• Uses a {pubId}/{fileName} key strategy, so that files are grouped by Pub. This might be a good strategy, but it also might not, because we might ultimately want to create a gallery that reuses assets across pubs? Idk. I don't think it's super important right now, but something to think on a little.

Supporting Docs

[3mcd]

I still need to test and provide feedback for the Zod and CSS import issues, but I went ahead and left a little bit of early feedback.

[3mcd]

We could use the expect function from "utils" to have a bit more granular error reporting here, like:

const region = expect(process.env.ASSETS_REGION, "ASSETS_REGION environment variable missing")
// ...

[3mcd]

Remove log statement.

[3mcd]

Some of our fields use snake-case e.g. "unjournal:evaluated-paper", so we should use that here or convert everything to camelCase. I have no strong feelings about either.

[3mcd]

A comment here explaining what fullFormats is doing would be helpful.