From 16e2f1548991db21dc5beea265983cebaf3f751a Mon Sep 17 00:00:00 2001
From: Fatih <66688048+AkgunFatih@users.noreply.github.com>
Date: Thu, 8 Oct 2020 03:25:53 +0200
Subject: [PATCH] Do not force cap_appname-gitea as a sub (#278)

let users decide the app name theirself
and don't force it as cap_appname-gitea.domain.com
---
 public/v4/apps/gitea.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/public/v4/apps/gitea.yml b/public/v4/apps/gitea.yml
index ca06a4f..038e524 100644
--- a/public/v4/apps/gitea.yml
+++ b/public/v4/apps/gitea.yml
@@ -12,7 +12,7 @@ services:
             MYSQL_PASSWORD: $$cap_db_pass
         caproverExtra:
             notExposeAsWebApp: 'true'
-    $$cap_appname-gitea:
+    $$cap_appname:
         depends_on:
             - $$cap_appname-db
         image: gitea/gitea:$$cap_gitea_version
@@ -49,7 +49,7 @@ caproverOneClickApp:
 
              Enter your Gitea Configuration parameters and click on next. A MySQL (database) and a Gitea container will be created for you. The process will take about a minute to finish.
         end: >
-            Gitea is deployed and available as $$cap_appname-gitea.
+            Gitea is deployed and available as $$cap_appname.
 
              Since Gitea is running inside a container, you can optionally map a port (not 22) of the host to port 22 of the container, if you want to use git commands over SSH. You can perform port mapping in your CapRover dashboard, in App Config section.