alex/voyage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename AdventureLog to Voyage and add fork attribution

Browse Source 
- Replace all AdventureLog references with Voyage across ~102 files
  (7 case variants: AdventureLog, adventurelog, Adventurelog, ADVENTURELOG,
  AdventUrelog, AdventureLOG, adventure-log, adventure_log)
- Rename brand, static, and documentation assets to use voyage naming
- Rename install_adventurelog.sh → install_voyage.sh
- Update README.md and voyage_overview.md to credit AdventureLog as
  the upstream project and Sean Morley as its original creator
This commit is contained in:
alex
2026-03-06 11:05:26 +00:00
parent 2b644d3afa
commit df8d1adf15
151 changed files with 653 additions and 658 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
documentation/docs/troubleshooting/nginx_failed.md
View File

@@ -1,10 +1,10 @@
# Troubleshooting: `Starting nginx: nginx failed!` in the Backend Container
::: tip
As of 1-10-2024, this should be resolved in the latest version of AdventureLog. If you are still experiencing this issue, please reach out to the AdventureLog community on Discord or GitHub for further assistance.
As of 1-10-2024, this should be resolved in the latest version of Voyage. If you are still experiencing this issue, please reach out to the Voyage community on Discord or GitHub for further assistance.
:::
The AdventureLog backend container uses a built-in Nginx container with a built-in nginx config that relies on the name `server` to be the service name of the backend container. If the Nginx service fails to start in the backend container, the whole backend service will keep restarting and fail to start.
The Voyage backend container uses a built-in Nginx container with a built-in nginx config that relies on the name `server` to be the service name of the backend container. If the Nginx service fails to start in the backend container, the whole backend service will keep restarting and fail to start.
**The primary reason for this error is changing the backend service name `server` to something different**
@@ -16,30 +16,30 @@ If you're experiencing issues with the Nginx service failing to start in the bac
- The service name should be set to `server` in the `docker-compose.yml` file. For example:
```yaml
server:
image: ghcr.io/seanmorley15/adventurelog-backend:latest
container_name: adventurelog-backend
image: ghcr.io/seanmorley15/voyage-backend:latest
container_name: voyage-backend
```
### 2. **To keep the backend service name different**:
- If you want to keep the backend service name different from `server`, you can mount a custom Nginx configuration file to the backend container.
- Get the default Nginx configuration file from the AdventureLog repository:
- Get the default Nginx configuration file from the Voyage repository:
```bash
wget https://raw.githubusercontent.com/seanmorley15/AdventureLog/refs/heads/main/backend/nginx.conf
wget https://raw.githubusercontent.com/seanmorley15/Voyage/refs/heads/main/backend/nginx.conf
```
- Update the `nginx.conf` file to replace all occurrences of `server` with your custom service name.
- Mount the custom Nginx configuration file to the backend container in the `docker-compose.yml` file. For example:
```yaml
server:
image: ghcr.io/seanmorley15/adventurelog-backend:latest
container_name: adventurelog-backend
image: ghcr.io/seanmorley15/voyage-backend:latest
container_name: voyage-backend
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf
```
### 3. **Restart the Backend Container**:
These steps should help you resolve the issue with the Nginx service failing to start in the backend container. If you continue to face issues, please reach out to the AdventureLog community on Discord or GitHub for further assistance.
These steps should help you resolve the issue with the Nginx service failing to start in the backend container. If you continue to face issues, please reach out to the Voyage community on Discord or GitHub for further assistance.