No Description

Pitu 399cce6f99 This is the last commit with tags 7 years ago
controllers d5c9b15ab9 Added username display on dashboard 7 years ago
database 13b2242bdf New database structure with users support 7 years ago
pages 399cce6f99 This is the last commit with tags 7 years ago
public 23f079516f MORE. META. DATA. 7 years ago
routes ec9de34cb3 Added changePassword 7 years ago
.DS_Store 3f4b879144 List and thumb view on uploads 7 years ago
.eslintrc.json 376cf10663 First version 7 years ago
.gitignore a7201c4b96 Added eslint because I don't know what im doing 7 years ago
LICENSE 8d2604cb51 Added license 7 years ago
README.md 79fee8defd Etooo 7 years ago
config.sample.js 93e5f6ab31 Added enableUserAccounts 7 years ago
lolisafe.js 999c148dff Changed /panel to /dashboard 7 years ago
package.json fbb8271658 Version bump 7 years ago

README.md

loli-safe

loli-safe

A small safe worth protecting.

Sites using loli-safe


  1. Clone
  2. Rename config.sample.js to config.js
  3. Modify port, basedomain and privacy 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

Getting started

This service supports running both as public and private. The only difference is that one needs a token to upload 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 set the option private: false in the config.js file. In case you want to run it privately, you should set private: true.

Upon running the service for the first time, it's gonna create a user account with the username root and password root. This is your admin account and you should change the password immediately. This account will let you manage all uploaded files and remove any if necessary.

If you set enableUserAccounts: true, people will be able to create accounts on the service to keep track of their uploaded files and create albums to upload stuff to, pretty much like imgur does, but only through the API. Every user account has a token that the user can use to upload stuff through the API. You can find this token on the section called Change your token on the administration dashboard, and if it gets leaked or compromised you can renew it by clicking the button titled Request new token.


Using loli-safe

Once the service starts you can start hitting the upload endpoint at /api/upload with any file. If you're using the frontend to do so then you are pretty much set, but if using the API to upload make sure the form name is set to files[] and the form type to multipart/form-data. If the service is running in private mode, dont forget to send a header of type token: YOUR-CLIENT-TOKEN to validate the request.

A sample of the returning json from the endpoint can be seen below:

{
	"name": "EW7C.png",
	"size": "71400",
	"url": "https://i.kanacchi.moe/EW7C.png"
}

To make it easier and better than any other service, you can download our Chrome extension that will let you configure your hostname and tokens, so that you can simply right click -> send to loli-safe to any image/audio/video file on the web.

Because of how nodejs apps work, if you want it attached to a domain name you will need to make a reverse proxy for it. Here is a tutorial on how to do this with nginx. Keep in mind that this is only a requirement if you want to access your loli-safe service by using a domain name (ex: https://i.kanacchi.moe), otherwise you can use the service just fine by accessing it from your server's IP.

If you choose to use a domain name and thus nginx, you should add the following directive into your location block with the limit you want to set on uploaded file's size: client_max_body_size 512M;

Author

loli-safe © Pitu, Released under the MIT License.
Authored and maintained by Pitu.

lolisafe.moe · GitHub @Pitu · Twitter @kanaadeko