Go to file
2024-04-16 23:02:19 -04:00
.nip05Storage/oceanslim readme 2024-04-16 23:02:19 -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 explicit relay list 2024-04-16 16:58:55 -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 changed port for upload server, readme update 2024-04-16 11:33:11 -04:00
server.js changed port for upload server, readme update 2024-04-16 11:33:11 -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) THIS IS CURRENTLY HARDCODED TO RUN ON PORT 34537 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?

grab preferred relays from nip (notepress has an example in setup.js) instead of using an explicit one.

Create directory for a user it doesn't already exist. UI think upload will fail right now if the user doesn't already have a directory

need provisions to catch if the user is uploading a file with the same name as a file already in their storage, ask to replace or rename the new file

config for max file size and default storage limit for a given user

can make a exceptions later to allow more storage for a user based on criterea

create a setup that runs both frontend and backend code and make a config file for any configs for the user

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

redo readme

make favicon

test on my site

release