From 2d06d918a154c15196ca92fb8f7873ca3c797f00 Mon Sep 17 00:00:00 2001 From: Pitu Date: Sat, 18 Jul 2020 02:21:31 +0900 Subject: Timeout, package and docs cleanup --- docs/migrating.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 docs/migrating.md (limited to 'docs/migrating.md') diff --git a/docs/migrating.md b/docs/migrating.md new file mode 100644 index 0000000..a7d9eb7 --- /dev/null +++ b/docs/migrating.md @@ -0,0 +1,14 @@ +### 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 +- 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. -- cgit v1.2.3 From 4dafc79cb74d901bb9454f78277298f020543bb5 Mon Sep 17 00:00:00 2001 From: Pitu Date: Sat, 18 Jul 2020 02:55:05 +0900 Subject: fix authorization --- docs/migrating.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/migrating.md') diff --git a/docs/migrating.md b/docs/migrating.md index a7d9eb7..796d422 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -12,3 +12,7 @@ For starters we recommend cloning the new version somewhere else instead of `git ### 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 +- You need to update the lolisafe browser if you use it, since it won't work with the new version automatically. Instead of pasting your token into it, 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 a file to. -- cgit v1.2.3 From aea442a9569a91b9610545978131f8dec0ab4ff3 Mon Sep 17 00:00:00 2001 From: Pitu Date: Sat, 18 Jul 2020 16:45:01 +0900 Subject: Update migration instructions --- docs/migrating.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'docs/migrating.md') diff --git a/docs/migrating.md b/docs/migrating.md index 796d422..6421391 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -5,14 +5,16 @@ For starters we recommend cloning the new version somewhere else instead of `git - 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 -- 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` +- 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 -- You need to update the lolisafe browser if you use it, since it won't work with the new version automatically. Instead of pasting your token into it, 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 a file to. +- 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. -- cgit v1.2.3 From 0b6867f1b1f490320126368304f6aaaca6807422 Mon Sep 17 00:00:00 2001 From: Pitu Date: Sat, 18 Jul 2020 16:45:51 +0900 Subject: update guide --- docs/migrating.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/migrating.md') diff --git a/docs/migrating.md b/docs/migrating.md index 6421391..ffd61ab 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -6,7 +6,7 @@ For starters we recommend cloning the new version somewhere else instead of `git - 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. +- This will migrate the v3 database to v4 and regenerate every single thumbnail in webp to save bandwidth. - 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`. -- cgit v1.2.3 From 37a5a8cce220a84ca151a1041b9aeaab2855f771 Mon Sep 17 00:00:00 2001 From: Pitu Date: Sat, 18 Jul 2020 16:50:39 +0900 Subject: Upgrade migration doc --- docs/migrating.md | 3 --- 1 file changed, 3 deletions(-) (limited to 'docs/migrating.md') diff --git a/docs/migrating.md b/docs/migrating.md index ffd61ab..9166581 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -11,9 +11,6 @@ For starters we recommend cloning the new version somewhere else instead of `git - 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. -- cgit v1.2.3 From ec2f9e0d989792c1760b48e063467cf6e59c580a Mon Sep 17 00:00:00 2001 From: Pitu Date: Fri, 25 Dec 2020 20:45:22 +0900 Subject: Rebrand --- docs/migrating.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/migrating.md') diff --git a/docs/migrating.md b/docs/migrating.md index 9166581..c622dff 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -9,9 +9,9 @@ For starters we recommend cloning the new version somewhere else instead of `git - This will migrate the v3 database to v4 and regenerate every single thumbnail in webp to save bandwidth. - 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`. +- And lastly start your chibisafe instance with `pm2 start pm2.json`. ### 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. +- If you are using the chibisafe 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/chibisafe-extension). +- The chibisafe browser extension needs your new token. Instead of pasting your jwt token into it like before, you need to log in to chibisafe, 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. -- cgit v1.2.3 From 4ff204115c92776b6277918925c4404ddcf55f72 Mon Sep 17 00:00:00 2001 From: Pitu Date: Mon, 4 Jan 2021 00:51:58 +0900 Subject: chore: update docs --- docs/migrating.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/migrating.md') diff --git a/docs/migrating.md b/docs/migrating.md index c622dff..f461c98 100644 --- a/docs/migrating.md +++ b/docs/migrating.md @@ -12,6 +12,6 @@ For starters we recommend cloning the new version somewhere else instead of `git - And lastly start your chibisafe instance with `pm2 start pm2.json`. ### Breaking changes -- If you are using the chibisafe 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/chibisafe-extension). +- If you are using the chibisafe extension from one of the stores, the new version has been submitted already. You can also load the unpacked extension by cloning [this repo](https://github.com/WeebDev/chibisafe-extension). - The chibisafe browser extension needs your new token. Instead of pasting your jwt token into it like before, you need to log in to chibisafe, 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. -- cgit v1.2.3