Skip to content
Open
Show file tree
Hide file tree
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
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,10 @@ By default, Appcircle uses seven subdomains. These subdomains are:
6. my.appcircle.spacetech.com
7. kvs.appcircle.spacetech.com

(Optional) If you are setting up the MCP server, create the following additional DNS entry:

8. mcp.appcircle.spacetech.com

**Upon completing the deployment** of the Appcircle server, you will need to create DNS records based on the Ingress objects created in Kubernetes.

</details>
Expand Down Expand Up @@ -493,6 +497,8 @@ appcircle-webeventredis nginx kvs.appcircle.spacetech.com
- `hook.appcircle.spacetech.com` → **api.appcircle.spacetech.com**
- `kvs.appcircle.spacetech.com` → **api.appcircle.spacetech.com**

- (Optional) `mcp.appcircle.spacetech.com` → **api.appcircle.spacetech.com**

### 2. Login to the Appcircle Dashboard

Check the output of the `helm install` command to see login URL, initial username and command to get initial user password.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,10 @@ By default, Appcircle uses seven subdomains. These subdomains are:
6. my.appcircle.spacetech.com
7. kvs.appcircle.spacetech.com

(Optional) If you are setting up the MCP server, create the following additional DNS entry:

8. mcp.appcircle.spacetech.com

**Upon completing the deployment** of the Appcircle server, you will need to create DNS records based on the routes created in OpenShift.

</details>
Expand Down Expand Up @@ -460,6 +464,8 @@ router-default LoadBalancer 10.217.4.108 10.45.140.78 80/TCP,443/TCP,1936/
- `hook.appcircle.spacetech.com` → **api.appcircle.spacetech.com**
- `kvs.appcircle.spacetech.com` → **api.appcircle.spacetech.com**

- (Optional) `mcp.appcircle.spacetech.com` → **api.appcircle.spacetech.com**

### 2. Login to the Appcircle Dashboard

Check the output of the `helm install` command to see login URL, initial username and command to get initial user password.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -492,6 +492,7 @@ Appcircle server has some subdomains for different services. So, you need to add
- monitor
- redis
- (optional) Enterprise App Store's Custom Domain
- (optional) MCP server DNS: mcp

:::info

Expand Down Expand Up @@ -545,6 +546,7 @@ On self-hosted Appcircle server, you should add below entries to the `/etc/hosts
0.0.0.0 monitor.appcircle.spacetech.com
0.0.0.0 redis.appcircle.spacetech.com
0.0.0.0 store.spacetech.com
0.0.0.0 mcp.appcircle.spacetech.com
```

For clients that will connect to self-hosted Appcircle server, either self-hosted runners or end-users using their browsers for web UI, should add external IP of the server to their `/etc/hosts` files. External IP is the address of self-hosted Appcircle server that other hosts in the network can reach to server using that address.
Expand All @@ -570,6 +572,7 @@ Other clients that connect to the server should add below entries to their `/etc
35.241.181.2 monitor.appcircle.spacetech.com
35.241.181.2 redis.appcircle.spacetech.com
35.241.181.2 store.spacetech.com
35.241.181.2 mcp.appcircle.spacetech.com
```

With this network setup, you can run and test both self-hosted Appcircle server and connected self-hosted runners with all functionality.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -518,6 +518,7 @@ Appcircle server has some subdomains for different services. So, you need to add
- monitor
- redis
- (optional) Enterprise App Store's Custom Domain
- (optional) MCP server DNS: mcp

:::info

Expand Down Expand Up @@ -571,6 +572,7 @@ On self-hosted Appcircle server, you should add below entries to the `/etc/hosts
0.0.0.0 monitor.appcircle.spacetech.com
0.0.0.0 redis.appcircle.spacetech.com
0.0.0.0 store.spacetech.com
0.0.0.0 mcp.appcircle.spacetech.com
```

For clients that will connect to self-hosted Appcircle server, either self-hosted runners or end-users using their browsers for web UI, should add external IP of the server to their `/etc/hosts` files. External IP is the address of self-hosted Appcircle server that other hosts in the network can reach to server using that address.
Expand All @@ -596,6 +598,7 @@ Other clients that connect to the server should add below entries to their `/etc
35.241.181.2 monitor.appcircle.spacetech.com
35.241.181.2 redis.appcircle.spacetech.com
35.241.181.2 store.spacetech.com
35.241.181.2 mcp.appcircle.spacetech.com
```

With this network setup, you can run and test both self-hosted Appcircle server and connected self-hosted runners with all functionality.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,9 @@ These subdomains are **api**, **auth**, **dist**, **hook**, **my**, **resource**
- [ ] `monitor.appcircle.spacetech.com`
- [ ] `redis.appcircle.spacetech.com`

- [ ] (Optional) If you are setting up the MCP server, create the following additional DNS entry on your DNS:
- [ ] `mcp.appcircle.spacetech.com`

- [ ] All of these domain names should resolve to the same server IP address, which is the Appcircle server.

You can see details in the [DNS Settings](/self-hosted-appcircle/install-server/linux-package/installation/docker#4-dns-settings) section.
Expand Down