Go to file
2024-04-16 10:05:34 -04:00
.nip05Storage/oceanslim working upload functionality 2024-04-16 10:05:34 -04:00
.well-known readme 2024-04-14 20:05:53 -04:00
.gitignore first commit 2024-04-14 20:04:50 -04:00
index.html first commit 2024-04-14 20:04:50 -04:00
index.js working upload functionality 2024-04-16 10:05:34 -04:00
package-lock.json working upload functionality 2024-04-16 10:05:34 -04:00
package.json working upload functionality 2024-04-16 10:05:34 -04:00
readme.md working upload functionality 2024-04-16 10:05:34 -04:00
server.js working upload functionality 2024-04-16 10:05:34 -04:00

pre req: get node js google it

install: clone the repo cd into it

install dependencies: npm install

run the dev server: vite

listen for uploads (run backend server) node server

go to http://localhost:5173 check out the console (right click inspect)

TODO: Check for security make sure I can't get around it some easy way at least. new npub with proper nip05 and username access? create a setup that runs both frontend and backend code and make a config file for any configs for the user

set up create path if it doesn't exist for a new user. config for max file size and default storage limit for a given iser can make a exceptions later to allow more storage for a user based on criterea

the .well-known and .nip05Storage are for testing purposed right now. they will be removed later.

redo readme

get rid of cors errors?

make favicon

test on my site

release