updated some thing relating to domainless setup
This commit is contained in:
17
deploy.sh
17
deploy.sh
@@ -257,9 +257,12 @@ cd /opt/dockge
|
|||||||
curl "https://dockge.kuma.pet/compose.yaml?port=5001&stacksPath=%2Fopt%2Fstacks" --output compose.yaml
|
curl "https://dockge.kuma.pet/compose.yaml?port=5001&stacksPath=%2Fopt%2Fstacks" --output compose.yaml
|
||||||
|
|
||||||
# write configuration to compose files
|
# write configuration to compose files
|
||||||
|
mkdir -p /opt/files
|
||||||
cp -r $scriptdir/stacks /opt
|
cp -r $scriptdir/stacks /opt
|
||||||
cp -r $scriptdir/setup /opt/stacks
|
cp -r $scriptdir/setup /opt/files
|
||||||
chmod -R 775 /opt/stacks
|
chmod -R 775 /opt/stacks
|
||||||
|
chmod -R 775 /opt/files
|
||||||
|
|
||||||
|
|
||||||
cd /opt/stacks
|
cd /opt/stacks
|
||||||
git clone https://github.com/trantienloi2404/youtube-downloader.git downloader
|
git clone https://github.com/trantienloi2404/youtube-downloader.git downloader
|
||||||
@@ -291,6 +294,14 @@ replace_string_recursive "/opt/stacks" "?bookstackdbrootpass?" $bookstackdbrootp
|
|||||||
#onlyofficeJWT
|
#onlyofficeJWT
|
||||||
replace_string_recursive "/opt/stacks" "?onlyofficeJWT?" $onlyofficeJWT
|
replace_string_recursive "/opt/stacks" "?onlyofficeJWT?" $onlyofficeJWT
|
||||||
|
|
||||||
|
#domain
|
||||||
|
replace_string_recursive "/opt/files" "?domain?" $domain
|
||||||
|
#publicip
|
||||||
|
replace_string_recursive "/opt/files" "?publicip?" $publicip
|
||||||
|
#localip
|
||||||
|
replace_string_recursive "/opt/files" "?localip?" $localip
|
||||||
|
#adminemail
|
||||||
|
replace_string_recursive "/opt/files" "?adminemail?" $adminemail
|
||||||
|
|
||||||
# install mailcow to /opt/stacks/mailcow so it shows up in dockge
|
# install mailcow to /opt/stacks/mailcow so it shows up in dockge
|
||||||
umask 0022
|
umask 0022
|
||||||
@@ -477,6 +488,10 @@ site.$domain
|
|||||||
Add any other subdomains you want to use.
|
Add any other subdomains you want to use.
|
||||||
EOF
|
EOF
|
||||||
|
|
||||||
|
cat >/opt/stacks/pihole/dns/02-wildcard.conf <<EOF
|
||||||
|
address=/?domain?/?localip?
|
||||||
|
EOF
|
||||||
|
|
||||||
echo ""
|
echo ""
|
||||||
echo ""
|
echo ""
|
||||||
echo ""
|
echo ""
|
||||||
|
|||||||
@@ -10,7 +10,7 @@ if [ -z "$DOMAIN" ]; then
|
|||||||
exit 1
|
exit 1
|
||||||
fi
|
fi
|
||||||
|
|
||||||
CERTS_DIR="/opt/stacks/browser/data/certs"
|
CERTS_DIR="/opt/files/certs/"
|
||||||
|
|
||||||
# Create certs directory if it doesn't exist
|
# Create certs directory if it doesn't exist
|
||||||
mkdir -p "$CERTS_DIR"
|
mkdir -p "$CERTS_DIR"
|
||||||
|
|||||||
@@ -1,17 +1,8 @@
|
|||||||
You can set up your cloud without purchasing a domain.
|
You can set up your cloud without purchasing a domain.
|
||||||
|
|
||||||
to do this, skip DNS setup during initial install, this means you cannot reach the various services via hostname yet.
|
for this, your pihole DNS is already set up to directly point ?domain? to ?localip?
|
||||||
|
|
||||||
Then, go to http://?localip?:5380 and log in with your admin password, this is your pihole dashboard.
|
as long as you are connected to the pihole DNS and on the local network, you will be able to reach your cloud.
|
||||||
|
|
||||||
go to settings > local dns records and add two records:
|
|
||||||
|
|
||||||
| domain | IP
|
|
||||||
| ?domain? | ?localip?
|
|
||||||
| *.?domain | ?localip?
|
|
||||||
|
|
||||||
|
|
||||||
now you can reach your cloud with whichever domain you want as long as you are on the pihole DNS.
|
|
||||||
|
|
||||||
The VPN is set up by default to use this DNS, so you will also be able to reach your cloud when using your VPN, allowing use on the go.
|
The VPN is set up by default to use this DNS, so you will also be able to reach your cloud when using your VPN, allowing use on the go.
|
||||||
|
|
||||||
|
|||||||
@@ -7,7 +7,6 @@ services:
|
|||||||
ports:
|
ports:
|
||||||
- 53:53/tcp
|
- 53:53/tcp
|
||||||
- 53:53/udp
|
- 53:53/udp
|
||||||
- 5380:80
|
|
||||||
environment:
|
environment:
|
||||||
TZ: ?timezone?
|
TZ: ?timezone?
|
||||||
FTLCONF_WEBSERVER_API_PASSWORD: ?adminpass?
|
FTLCONF_WEBSERVER_API_PASSWORD: ?adminpass?
|
||||||
|
|||||||
Reference in New Issue
Block a user