This fork is the one being used at https://safe.fiery.me.
It was originally based on WeebDev/lolisafe v3, but later have been so heavily rewritten that it is now simply its own thing.
Chibisafe is an upstream rewrite & rebrand, and technically is lolisafe v4.
If you want to use an existing lolisafe v3 database with this fork, copy over database/db
file from your previous installation, then run yarn migrate
at least once to create the new database columns introduced in this fork (don't forget to make a backup).
[!CAUTION]
The migration script is NOT COMPATIBLE with Chibisafe's database.
Configuration file of lolisafe v3 (config.js
) is also NOT fully compatible with this fork. There are some options that had been renamed and/or restructured
Please make sure your config matches the sample in config.sample.js
before starting and/or migrating your previous database (hint: this fork's default config assumes your database file is named db.sqlite3
instead of db
).
[!NOTE]
Compatible up to Node.js v20.x.
I recommend using Volta to ensure you will always have & use the correct Node.js and Yarn versions for lolisafe, even if the requirements change in future updates.If you want to use this on Docker, please check out the docker directory instead.
config.sample.js
as config.js
.views/_globals.sample.njk
as views/_globals.njk
.yarn install --production
to install all production dependencies.yarn start
to start lolisafe. Alternatively, you can also start lolisafe with yarn pm2
if you have PM2 installed.[!NOTE]
If you see errors related to sharp engines upon starting lolisafe, try to runyarn install --production --ignore-engines
first.[!IMPORTANT]
Default admin/root account:
Username:root
Password:changeme
When running in production mode, lolisafe will use pre-built client-side CSS/JS files from dist
directory, while the actual source codes are in src
directory.
The pre-built files are processed with postcss-preset-env, cssnano, bublé, and terser, and done automatically with GitHub Actions.
This fork has a separate development mode, with which client-side CSS/JS files in src
directory will be automatically rebuilt using Gulp tasks.
yarn install
to install all dependencies (by omitting --production
option, Yarn will also install development dependencies).yarn dev
to start lolisafe in development mode (or yarn dev:reload
to also watch file changes).You can further modify the Gulp tasks through gulpfile.js
file.
During development, the rebuilt files will be saved in dist-dev
directory instead of dist
directory. Lolisafe will also automatically serve the files from dist-dev
directory instead.
This is to ensure that your IDE's Git extension will not unnecessarily rebuild diffs of the modified files.
Once you feel like your modifications are ready for production usage, you can then run yarn build
to build production-ready files that will actually go to dist
directory.
[!TIP]
If you are submitting a Pull Request, please do not stage any changes to files indist
directory.
GitHub Actions will automatically rebuild those assets if and when required.
Try to use git stash.
Basically you'll be doing this:
git stash
to stash away your changes.git pull
to pull updates.yarn install
(or yarn install --production
) to install dependencies matching the updated yarn.lock
file.git stash pop
(or git stash apply
) to restore your changes.Be warned that some files may have been updated too heavily that they will require manual merging.
If you only do some small modifications such as editing .njk
files and not much else, it's generally safe to do this even in a live production environment. But it's still best practice to at least review just what have been updated, and whether you will need to do some manual merging beforehand.
Still, I heavily recommend simply forking this repository and manually merging upstream changes whenever you feel like doing so. Read more about syncing a fork. Especially if you intend to modify client-side CSS/JS files in src
directory, since you will then need to rebuild assets that go into dist
directory, which are guaranteed to always conflict with every updates from this fork that modify them.
Afterwards, you can instead clone your fork into your production server and pull updates from there. You can then choose to only install production dependencies with yarn install --production
there to save some disk space (hint: this is the workflow I use for https://safe.fiery.me).
This fork has an optional virus scanning support using ClamAV, utilizing clamscan library (Linux and OS X only).
It will scan new files right after they are uploaded, then alert the uploaders of the virus names in ClamAV's database if the files are dirty.
Unfortunately, this will slow down uploads processing as it has to wait for the scans before responding the uploaders. However, it's still highly recommended for public usage, or if you're like me who find the constant buzzing from Google Safe Search too annoying.
To enable this, make sure you have ClamAV installed, or additionally have ClamAV daemon running (using daemon is considerably faster). Afterwards, configure uploads.scan
options, and more importantly its sub-option clamOptions
. Read more about them in config.sample.js
.
Additionally, you can also configure usergroups bypass, extensions whitelist, and max file size, to lessen the burden on your server.