Blazing fast file uploader and awesome bunker written in node! 🚀
Go to file
2017-01-14 18:13:58 -03:00
controllers Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00
database Frontend done 2017-01-14 05:50:18 -03:00
public Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00
routes Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00
.DS_Store Removed unused files 2017-01-14 06:16:47 -03:00
.eslintrc.json First version 2017-01-13 04:34:21 -03:00
.gitignore Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00
config.sample.js Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00
lolisafe.js Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00
package.json Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00
README.md Changed from ip whitelist to token based auth 2017-01-14 18:13:58 -03:00

loli-safe

loli-safe

Pomf-like image uploading service, written in NodeJS


  1. Clone
  2. Rename config.sample.js to config.js
  3. Modify port and token options if desired
  4. run npm install to install all dependencies
  5. run pm2 start lolisafe.js or node lolisafe.js to start the service

Token

This service supports running both as public and private. The only difference is that one needs a token and the other one doesn't. If you want it to be public so anyone can upload files either from the website or API, just leave the token empty on the config file.

But if you want to run it privately, you need to specify a random string, which you'll need to provide in every API call as a header called auth.


Using it

After the service is started, you can POST files to /api/upload . The file key needs to be called file and it should be a multipart/form-data upload, or else it will be disregarded.

This works great with sharex, just like cuntflaps.me and mixtape.moe. A chrome extension to be able to right click images -> send to safe is in the works.

If you are using nginx, you should set inside your location block the following directive, replacing the number with the one you want set up client_max_body_size 512M;

If using apache, you should change the following directives on your config RLimitMEM 512M