mirror of
				https://github.com/jakeswenson/BitBetter.git
				synced 2025-10-31 12:53:25 +00:00 
			
		
		
		
	Updated version, created update section
This commit is contained in:
		
							parent
							
								
									9c800718cb
								
							
						
					
					
						commit
						a50041dead
					
				|  | @ -13,6 +13,7 @@ Credit to https://github.com/h44z/BitBetter and https://github.com/jakeswenson/B | ||||||
|     + [Dependencies](#dependencies) |     + [Dependencies](#dependencies) | ||||||
|     + [Setting up BitBetter](#setting-up-bitbetter) |     + [Setting up BitBetter](#setting-up-bitbetter) | ||||||
|     + [Building BitBetter](#building-bitbetter) |     + [Building BitBetter](#building-bitbetter) | ||||||
|  |     + [Updating Bitwarden and BitBetter](#updating-bitwarden-and-bitbetter) | ||||||
|     + [Generating Signed Licenses](#generating-signed-licenses) |     + [Generating Signed Licenses](#generating-signed-licenses) | ||||||
| 2. [FAQ](#faq-questions-you-might-have-) | 2. [FAQ](#faq-questions-you-might-have-) | ||||||
| 3. [Footnotes](#footnotes) | 3. [Footnotes](#footnotes) | ||||||
|  | @ -23,7 +24,7 @@ The following instructions are for unix-based systems (Linux, BSD, macOS), it is | ||||||
| ## Dependencies | ## Dependencies | ||||||
| Aside from docker, which you also need for Bitwarden, BitBetter requires the following: | Aside from docker, which you also need for Bitwarden, BitBetter requires the following: | ||||||
| 
 | 
 | ||||||
| * Bitwarden (tested with 1.33.0, might work on lower versions) | * Bitwarden (tested with 1.34.0, might work on lower versions) | ||||||
| * openssl (probably already installed on most Linux or WSL systems, any version should work) | * openssl (probably already installed on most Linux or WSL systems, any version should work) | ||||||
| 
 | 
 | ||||||
| ## Setting up BitBetter | ## Setting up BitBetter | ||||||
|  | @ -63,7 +64,6 @@ You'll also want to edit the `/path/to/bwdata/scripts/run.sh` file. In the `func | ||||||
| 
 | 
 | ||||||
| You can now start or restart Bitwarden as normal and the modified api will be used. **It is now ready to accept self-issued licenses.** | You can now start or restart Bitwarden as normal and the modified api will be used. **It is now ready to accept self-issued licenses.** | ||||||
| 
 | 
 | ||||||
| To update Bitwarden, the provided `update-bitwarden.sh` script can be used. It will rebuild the BitBetter images and automatically update Bitwarden afterwards. Docker pull errors can be ignored for api and identity images. |  | ||||||
| --- | --- | ||||||
| ### Note: Manually generating Certificate & Key | ### Note: Manually generating Certificate & Key | ||||||
| 
 | 
 | ||||||
|  | @ -79,6 +79,10 @@ openssl pkcs12 -export -out cert.pfx -inkey key.pem -in cert.pem -passin pass:te | ||||||
| 
 | 
 | ||||||
| --- | --- | ||||||
| 
 | 
 | ||||||
|  | ## Updating Bitwarden and BitBetter | ||||||
|  | 
 | ||||||
|  | To update Bitwarden, the provided `update-bitwarden.sh` script can be used. It will rebuild the BitBetter images and automatically update Bitwarden afterwards. Docker pull errors can be ignored for api and identity images. | ||||||
|  | 
 | ||||||
| ## Generating Signed Licenses | ## Generating Signed Licenses | ||||||
| 
 | 
 | ||||||
| There is a tool included in the directory `src/licenseGen/` that will generate new individual and organization licenses. These licenses will be accepted by the modified Bitwarden because they will be signed by the certificate you generated in earlier steps. | There is a tool included in the directory `src/licenseGen/` that will generate new individual and organization licenses. These licenses will be accepted by the modified Bitwarden because they will be signed by the certificate you generated in earlier steps. | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue
	
	Block a user