Go to file
Pitu 9367eb5eb8 Merge branch 'master' of github.com:WeebDev/lolisafe 2022-01-14 01:05:46 +09:00
.github Create FUNDING.yml 2020-02-28 09:28:12 +09:00
.vscode Cleanup 2020-12-25 02:08:54 +09:00
docker fix: docker script 2021-06-20 03:54:45 +09:00
docs Remove safe.fiery.moe from sites.md (#317) 2022-01-13 23:19:04 +09:00
src Allow API Access to some endpoints (#304) 2021-11-03 22:17:34 +09:00
.dockerignore add docker support 2020-12-26 21:00:53 +01:00
.editorconfig More stuff 2019-02-19 00:06:55 +09:00
.gitattributes More stuff 2019-02-19 00:06:55 +09:00
.gitignore feat: add dynamic settings page rendering based on the Joi object 2021-01-10 02:04:35 +02:00
.npmrc add docker support 2020-12-26 21:00:53 +01:00
README.md chore: docs update 2021-06-07 17:40:28 +09:00
babel.config.js chore: docs update 2021-06-07 17:40:28 +09:00
jest.config.js feat: add testing capabilities 2021-01-04 00:48:34 +09:00
knexfile.js fix: database location 2020-12-25 04:10:52 +09:00
nuxt.config.js fix: pulling config from the db during build process 2021-06-20 21:16:56 +09:00
package-lock.json chore: change to sass 2022-01-14 01:05:43 +09:00
package.json chore: change to sass 2022-01-14 01:05:43 +09:00
pm2.json Rebrand 2020-12-25 20:45:22 +09:00


GitHub license Chat / Support Support me Support me


If you are upgrading from v3.x to v4.0.0 (lolisafe to chibisafe) and you want to keep your files and relations please read the migration guide. Keep in mind the migration is a best-effort script and it's recommended to start from scratch. That being said the migration does work but it's up to you to make a backup beforehand in case something goes wrong.

v4.0.1 changed the hashing algorithm for a better, faster one. So if you are currently running v4.0.0 and decide to update to v4.0.1+ it's in your best interest to rehash all the files your instance is serving. To do this go to the chibisafe root folder and run node src/api/utils/rehashDatabase.js. Depending on how many files you have it can take a few minutes or hours, there's a progress bar that will give you an idea.

What is Chibisafe?

Chibisafe is a file uploader service written in node that aims to to be easy to use and easy to set up. It's mainly intended for images and videos, but it accepts anything you throw at it.

  • You can run it in public or private mode, making it so only people with user accounts can upload files as well as controlling if user signup is enabled or not.
  • Out of the box support for ShareX configuration letting you upload screenshots and screenrecordings directly to your chibisafe instance.
  • Browser extension to be able to right click any image/video from any website and upload it directly to your chibisafe instance.
  • Chunk uploads enabled by default to be able to handle big boi files.
  • API Key support so you can integrate the service with whatever you desire.
  • Albums, tags and Discord-like search function
  • User list and control panel


If you want to deploy a docker instance instead of manually setting the service up, you can use docker-composer with our scripts. Please refer to the docs here


This guide asumes a whole lot of things, including that you know your way around linux, nginx and internet in general.

  • Decently updated version of linux (we recommend Debian)
  • node version 12.18.2+ (we recommend using volta.sh or n)
  • build-essential package installed in your system to build dependencies
  • ffmpeg package installed
  • pm2 globally installed (npm i -g pm2) to keep the service alive at all times.
    • Alternatively you can use tmux, forever, or whatever you are most familiar with
  • nginx installed and running

Note: while Chibisafe does work on Windows, setting it up is not covered in this readme. It's up to you to install the neccessary dependencies


  1. Clone the repository and cd into it
  2. Run npm i
  3. Run npm run setup

Chibisafe is now installed, configured and ready. Now you need to serve it to the public by using a domain name.

  1. Check the nginx file for a sample configuration that has every step to run chibisafe securely on production.

After you finish setting up nginx, you need to start chibisafe by using pm2. If you want to use something else like forever, ensure that the process spawned from npm run start never dies.

  1. Run pm2 start pm2.json:
  2. Profit



Chibisafe © Pitu, Released under the MIT License.
Authored and maintained by Pitu.

chibisafe.moe · GitHub @Pitu