github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-04-27 17:48:17 -05:00
Code Issues 1.3k Packages Projects Releases 54 Wiki Activity

whitespace fixes (#522)

Browse Source 
Removes double spacing and trailing whitespace.
This commit is contained in:
Matt Fiddaman
2024-11-28 20:40:12 +00:00
committed by GitHub
parent bd2d1cce30
commit 1faead2732
43 changed files with 357 additions and 357 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/config/https.md
View File

@@ -14,16 +14,16 @@ Use a self-signed certificate. This is the easiest way to get HTTPS working, but
- A command line tool like [mkcert](https://github.com/FiloSottile/mkcert) can automate this process.
- Alternately, you can manually generate the certificates. Install OpenSSL for your operating system, then run `openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout selfhost.key -out selfhost.crt` in a terminal to generate the certificate and private key. You’ll need to enter a two-letter country code to get the `.crt` file to be generated, but you can leave the rest of the fields blank (just hit enter at each prompt). Move the `selfhost.key` and `selfhost.crt` files to a location accessible to the Actual server.
### Obtain a certificate without exposing to the internet
### Obtain a certificate without exposing to the internet
Use a service like [Tailscale](https://tailscale.com/kb/1153/enabling-https/) or [Caddy](https://caddyserver.com/docs/automatic-https#dns-challenge) that allows you to create a valid HTTPS certificate without having to expose your server to the wider internet.
## 2. Configure Actual to use the certificate
Once you have the certificate, you’ll need to configure Actual to use it. There are two methods to do this:
### Configuring with `config.json`:
Create a `config.json` file in the same folder where you run Actual. Put the paths to the `.key` and `.crt` files in the file. Note: if you’re using Docker or a similar container environment, make sure the paths are accessible to the container.
### Configuring with `config.json`:
Create a `config.json` file in the same folder where you run Actual. Put the paths to the `.key` and `.crt` files in the file. Note: if you’re using Docker or a similar container environment, make sure the paths are accessible to the container.
If using a Docker container, this folder is `/data` within the container. If you mounted a volume for the container, the folder on the host where `/data` is mounted is where you can place the `config.json` file.
If using a Docker container, this folder is `/data` within the container. If you mounted a volume for the container, the folder on the host where `/data` is mounted is where you can place the `config.json` file.
`config.json`:
@@ -35,12 +35,12 @@ If using a Docker container, this folder is `/data` within the container. If you
}
}
```
### Configuring with environment variables:
### Configuring with environment variables:
If you can’t easily create new files, you can also configure HTTPS using environment variables. Set the `ACTUAL_HTTPS_KEY` and `ACTUAL_HTTPS_CERT` environment variables to the contents of the `.key` and `.crt` files, respectively. If you’re unable to include newlines in the environment variable values, you can replace any newlines with `\n` and Actual will automatically convert them back to newlines.
### Configuring the Desktop App:
To configure the desktop app, follow these steps on the _Where's the server?_ screen.
### Configuring the Desktop App:
To configure the desktop app, follow these steps on the _Where's the server?_ screen.
1. Enter your server URL and click OK.
2. If you see an error message asking you to select your certificate, choose the appropriate certificate and try again.