abdallah
/
one-click-apps
1
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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
This commit is contained in:
Fatih 2020-10-08 03:25:53 +02:00 committed by GitHub
parent bc09ff24c4
commit 16e2f15489
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
public/v4/apps/gitea.yml
View File

@ -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.