Go to file
2024-05-25 00:28:08 -04:00
build changes 2024-05-23 12:15:02 -04:00
conf changes 2024-05-23 12:15:02 -04:00
src e 2024-05-25 00:28:08 -04:00
.gitignore add en_CAT makefile and use ucfirst/ucwords 2024-04-05 15:00:27 -04:00
docker-compose.yml changes 2024-05-23 12:15:02 -04:00
LICENSE v2 done 2024-05-20 17:11:38 -04:00
README.md v2 done 2024-05-20 17:11:38 -04:00

xssbook

description

who doesn't want to run non free javascript

now with xssbook you can run as much stallman disapprovement as you want

  • all inputs on the site are unfiltered
  • api calls dont care what you send them as long as they are valid strings
  • upload anyfiles to be your profile avatar and banner (even adobe flash!!!)
  • /apidocs for api documentation

installation

XXSBook v2 is a multi docker image setup. To run, download the repoistory, build the docker images, and then start the stack.

# download the images
git clone https://g.freya.cat/freya/xssbook2 xssbook2
cd xssbook2
# build and run the stack
docker compose pull
docker compose build
docker compose up -d

The only configuration that you many want to change is the http port listed in the docker compose file. By default this is set to port 80, but it can be changed to whatever you want.

migrating from xssbook v1

If you are runing a xssbook v1 setup, the database is fully incompatible with xssbook v2. Luckily there is a migration that exists to port over your data. XSSBook v1 has a single sqlite database file and a custom assets directory likly called custom. You will know you have the right directory if there are two sub directories called avatar and banner. Place the sqlite db file (called xssbook.db) and the custom directory in the data/shim folder of the xssbook v2 directory. If this doesnt exist please do a full setup of v2 first. Then run docker compose up -d shim, and you should be all set.

WARNING: This will delete ALL data in the database if you specify xssbook v1 files in the data path. Make sure yo only run this once and remove the files once completed.

NOTE: the migration will never run if the database files are not supplied.

license

This project is licensed under the MIT license