v3.0.0/docs/migrating.md

### Migrate from v3 to v4
This version introduces a few breaking changes and updating requires some manual work.
For starters we recommend cloning the new version somewhere else instead of `git pull` on your v3 version.

- After cloning move your `uploads` folder from the v3 folder to the new v4 folder.
- Then copy your `database/db` file from your v3 folder to the root of your v4 folder.
- You then need to run `yarn setup` or `npm start setup` from the v4 folder and finish the setup process.
- Once that's done you need to manually run `node src/api/databaseMigration.js` from the root folder of v4.
- This will migrate the v3 database to v4 and regenerate every single thumbnail to acomodate the new format.
- After the migration finishes, the last step is to update your nginx config with the [newly provided script](./nginx.md).
- Restart nginx with `sudo nginx -s reload`.
- And lastly start your lolisafe instance with `pm2 start pm2.json`.

### Known issues of migrating
- The thumbnails in the album view don't show up. That's because they don't exist, this will get solved as you upload new stuff so the newly uploaded files get the proper thumbnail created.

### Breaking changes
- If you are using the lolisafe extension from one of the stores, the new version has been submitted and could take up to a week to get approved. In the meantime you can load the unpacked extension by cloning [this repo](https://github.com/WeebDev/loli-safe-extension).
- The lolisafe browser extension needs your new token. Instead of pasting your jwt token into it like before, you need to log in to lolisafe, go to your user settings and generate an `API KEY`, which you will use to access the service from 3rd party apps like the browser extension, ShareX, etc.
- To upload a file to an album directly users used to use the endpoint `/api/upload/${albumId}`. This is no longer the case. To upload directly to an album now it's necessary to pass a header called `albumid` with an integer as the value of the album to which you want to upload the file to.
Timeout, package and docs cleanup 2020-07-17 19:21:31 +02:00			`### Migrate from v3 to v4`
			`This version introduces a few breaking changes and updating requires some manual work.`
			For starters we recommend cloning the new version somewhere else instead of `git pull` on your v3 version.

			- After cloning move your `uploads` folder from the v3 folder to the new v4 folder.
			- Then copy your `database/db` file from your v3 folder to the root of your v4 folder.
			- You then need to run `yarn setup` or `npm start setup` from the v4 folder and finish the setup process.
Update migration instructions 2020-07-18 09:45:01 +02:00			- Once that's done you need to manually run `node src/api/databaseMigration.js` from the root folder of v4.
			`- This will migrate the v3 database to v4 and regenerate every single thumbnail to acomodate the new format.`
			`- After the migration finishes, the last step is to update your nginx config with the [newly provided script](./nginx.md).`
			- Restart nginx with `sudo nginx -s reload`.
			- And lastly start your lolisafe instance with `pm2 start pm2.json`.
Timeout, package and docs cleanup 2020-07-17 19:21:31 +02:00
			`### Known issues of migrating`
			`- The thumbnails in the album view don't show up. That's because they don't exist, this will get solved as you upload new stuff so the newly uploaded files get the proper thumbnail created.`
fix authorization 2020-07-17 19:55:05 +02:00
			`### Breaking changes`
Update migration instructions 2020-07-18 09:45:01 +02:00			`- If you are using the lolisafe extension from one of the stores, the new version has been submitted and could take up to a week to get approved. In the meantime you can load the unpacked extension by cloning [this repo](https://github.com/WeebDev/loli-safe-extension).`
			- The lolisafe browser extension needs your new token. Instead of pasting your jwt token into it like before, you need to log in to lolisafe, go to your user settings and generate an `API KEY`, which you will use to access the service from 3rd party apps like the browser extension, ShareX, etc.
			- To upload a file to an album directly users used to use the endpoint `/api/upload/${albumId}`. This is no longer the case. To upload directly to an album now it's necessary to pass a header called `albumid` with an integer as the value of the album to which you want to upload the file to.