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

30
documentation/docs/install/nginx_proxy_manager.md
View File

@@ -2,26 +2,26 @@
Nginx Proxy Manager is a simple and powerful tool that allows you to manage Nginx proxy hosts and SSL certificates. It is designed to be easy to use and configure, and it integrates well with Docker.
It is fairly simple to set up Nginx Proxy Manager with AdventureLog.
It is fairly simple to set up Nginx Proxy Manager with Voyage.
## Deploy AdventureLog using Docker
## Deploy Voyage using Docker
View the [Docker installation guide](docker.md) for instructions on how to deploy AdventureLog using Docker.
View the [Docker installation guide](docker.md) for instructions on how to deploy Voyage using Docker.
## Ensure Correct Environment Variables
- `ORIGIN` - The domain where you will be hosting AdventureLog. This is where the **frontend** will be served from.
- `ORIGIN` - The domain where you will be hosting Voyage. This is where the **frontend** will be served from.
- `PUBLIC_URL` - This needs to match the **outward port of the server** and be accessible from where the app is used. It is used for the creation of image URLs.
## Setup Docker Network
Ensure that the Nginx Proxy Manager and AdventureLog containers are on the same Docker network. You can create a new network using the following command:
Ensure that the Nginx Proxy Manager and Voyage containers are on the same Docker network. You can create a new network using the following command:
```bash
docker network create nginx-proxy-manager
```
Add the following to the bottom of the `docker-compose.yml` file for the Nginx Proxy Manager service and the AdventureLog service.
Add the following to the bottom of the `docker-compose.yml` file for the Nginx Proxy Manager service and the Voyage service.
```yaml
networks:
@@ -34,15 +34,15 @@ networks:
1. Install Nginx Proxy Manager on your server. You can find the installation instructions [here](https://nginxproxymanager.com/setup/).
2. Open the Nginx Proxy Manager web interface and log in with your credentials.
3. Add a new proxy host for the AdventureLog **frontend**:
- **Domain Names**: Enter the domain name where you will be hosting AdventureLog.
3. Add a new proxy host for the Voyage **frontend**:
- **Domain Names**: Enter the domain name where you will be hosting Voyage.
- **Scheme**: `http`
- **Forward Hostname/IP**: `adventurelog-frontend` The name of the AdventureLog **frontend** container in the `docker-compose.yml` file.
- **Forward Port**: `3000` This is the internal port of the AdventureLog **frontend** container so you will not need to change it even if you change the external port.
4. Add a new proxy host for the AdventureLog **backend**:
- **Domain Names**: Enter the domain name where you will be hosting AdventureLog.
- **Forward Hostname/IP**: `voyage-frontend` The name of the Voyage **frontend** container in the `docker-compose.yml` file.
- **Forward Port**: `3000` This is the internal port of the Voyage **frontend** container so you will not need to change it even if you change the external port.
4. Add a new proxy host for the Voyage **backend**:
- **Domain Names**: Enter the domain name where you will be hosting Voyage.
- **Scheme**: `http`
- **Forward Hostname/IP**: `adventurelog-backend` The name of the AdventureLog **backend** container in the `docker-compose.yml` file.
- **Forward Port**: `80` This is the internal port of the AdventureLog **backend** container so you will not need to change it even if you change the external port.
- **Forward Hostname/IP**: `voyage-backend` The name of the Voyage **backend** container in the `docker-compose.yml` file.
- **Forward Port**: `80` This is the internal port of the Voyage **backend** container so you will not need to change it even if you change the external port.
This will allow you to access AdventureLog using the domain name you specified in the Nginx Proxy Manager configuration.
This will allow you to access Voyage using the domain name you specified in the Nginx Proxy Manager configuration.