Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

small 67 follow up with fixes/clarifications #70

Merged
merged 1 commit into from
Oct 16, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/software/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -271,11 +271,11 @@ Once you managed to install Jam, make sure to understand how to use it.

[:octicons-arrow-right-24: First Use][cheatsheet]

### ... installing `jmwalletd`, `ob-watcher` and `jam` services (optional but recommended)
The following will setup three services that run at startup, so you don't need to manually start Jam or any related daemon. That is, every time reboot your server, you can access Jam via the URL you have configured (e.g. 127.0.0.1:3000 or similar) without any further action.
### ... Configure to run `jmwalletd`, `ob-watcher` and `jam` services at start up(optional but recommended)
The following will setup three services that run at startup, so you don't need to manually start Jam or any related daemon. That is, every time you boot your server, you can access Jam via the URL you have configured (e.g. 127.0.0.1:3000 or similar) without any further action.

The service scripts below assume standard joinmarket structure, such as:
Working directory: `/home/joinmarket/.joinmarket`
Working/data directory: `/home/joinmarket/.joinmarket`
Main joinmarket directory: `/home/joinmarket/joinmarket-clientserver`
User and group: `joinmarket` and `joinmarket`

Expand Down Expand Up @@ -369,7 +369,7 @@ sudo systemctl start ob-watcher
sudo systemctl start jam
```

#### Knowing if any of the services are starting at boot
#### Verify that the services are starting at boot
These commands will tell you which of your services is set to start at boot:
```sh
systemctl is-enabled jmwalletd.service
Expand Down