.fs is a mostly-fully-featured, self-hosted, open-source, and extremely easy to deploy solution for hosting your own personal file sharing service. All you need to start is a Vercel free tier account, an AWS free tier S3 bucket, and a MongoDB Atlas free tier DB.
Fork this repo, and open it up in a code editor (like VSCode). What you'll want to do now is make a copy of .env.example and rename your copy to .env.local.
run npm i
You'll need to have a free-tier (or pay as you go) AWS account for this step. If you don't have an account yet, sign up using this link.
Once logged in to AWS, you'll first want to go to the S3 tab, and create a new NON-ACL, NON-VERSIONED bucket (optionally) named after your domain where you'll host this on. For example, if you have a domain example.com, you'll name your bucket dotfs.example.com and setup a CNAME DNS record from dotfs.example.com to point to the actual bucket URL, which will look something like https://<bucket-name>.s3.<region>.amazonaws.com/. Note that you don't need to name your bucket this; however, you will need to modify the AWS_URL to match your full bucket url.
Please make sure to uncheck the above boxes.
Next, add the bucket url you just created to the .env.local you made earlier in the requisite variable.
Then, go to the bucket's Permissions page, scroll down, and edit the CORS configuration. Paste in the following code block, but make sure to replace the sections in brackets:
[
{
"AllowedHeaders": [
"*"
],
"AllowedMethods": [
"POST",
"GET",
"PUT",
"DELETE",
"HEAD"
],
"AllowedOrigins": [
"https://[your-aws-bucket-domain]",
"https://[your-site-subdomain]",
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
]
Now, head over to the bucket's Management tab. You'll want to create the above listed rules, each of them having the same structure as shown in the following image, except for the day counts. This is part of what allows the auto-deletion to work. They must have the tags exactly as shown.
Finally, for AWS, the last thing you need to do is create a user and IAM service credentials so that .fs can access your AWS bucket. You can name the user whatever you want, but please make sure to select Attach Policies Directly and then add the AmazonS3FullAccess policy to allow this account full access. Then, create the account's credentials by going into the user's panel > Security Credentials and scroll down to Access Keys, and click Create Access Key.
You'll want to select Application Running Outside AWS and ignore the warning that comes up, and then copy and paste the credentials into your .env.local file in their requisite spots. This is the only time you'll be able to see these creds, so make sure to either take a pic or immediately copy them down.
TODO