a790d7749e
For now, it sitll requires gifski. It could be rewritten to use webp instead of gifs, because that is a lot faster, uses less space and we could use ffmpeg for it. |
||
---|---|---|
.vscode | ||
docs | ||
src | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.prettierrc | ||
README.md | ||
TODO | ||
knexfile.js | ||
nuxt.config.js | ||
package.json | ||
pm2.json | ||
yarn.lock |
README.md
Pre-requisites
This guide asumes a lot of things, including that you know your way around linux, nginx and internet in general.
- Decently updated version of linux
node
package installed and at least at version 10build-essential
package installed to build some dependenciesffmpeg
package installed if you want thumbnailsyarn
package installed. If you'd like to use npm instead changepackage.json
accordingly- A database, postgresql preferably. You can also fall back to sqlite3 by default.
Installing
- Clone the repository and
cd
into it - Run
yarn install
- Run
yarn setup
- Run
yarn migrate
- Run
yarn seed
Lolisafe is now installed, configured and ready. Now you need to serve it to the public by using a domain name.
- Check the nginx file for a sample configuration that has every step to run lolisafe securely on production.
After you finish setting up nginx, you need to start lolisafe by using pm2. If you want to use something else, figure out how. (More info on why pm2 here)
- Run
pm2 start pm2.json
: - Profit
Cloudflare
If you want to run your site through CloudFlare because of the obvious advantages it has, lolisafe has your back. Unless you manually modify the .env
file, uploads through the website will be uploaded in chunks thus bypassing CloudFlare's 100mb upload limit per file.
Author
lolisafe © Pitu, Released under the MIT License.
Authored and maintained by Pitu.
lolisafe.moe · GitHub @Pitu