use https in ci test

This commit is contained in:
aptalca 2025-07-07 11:03:04 -04:00
parent 3bfc0584ce
commit 7c5e2f46b0
No known key found for this signature in database
GPG Key ID: BE36CFFB9FD85548
3 changed files with 9 additions and 4 deletions

4
Jenkinsfile vendored
View File

@ -30,8 +30,8 @@ pipeline {
MULTIARCH = 'true'
CI = 'true'
CI_WEB = 'true'
CI_PORT = '8080'
CI_SSL = 'false'
CI_PORT = '8181'
CI_SSL = 'true'
CI_DELAY = '120'
CI_DOCKERENV = ''
CI_AUTH = ''

View File

@ -61,6 +61,11 @@ The container can be accessed at:
* http://yourhost:8080/
* https://yourhost:8181/
### Strict reverse proxies
This image uses a self-signed certificate by default. This naturally means the scheme is `https`.
If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
### Hardware Acceleration
Many desktop applications need access to a GPU to function properly and even some Desktop Environments have compositor effects that will not function without a GPU. However this is not a hard requirement and all base images will function without a video device mounted into the container.

View File

@ -20,8 +20,8 @@ repo_vars:
- MULTIARCH = 'true'
- CI = 'true'
- CI_WEB = 'true'
- CI_PORT = '8080'
- CI_SSL = 'false'
- CI_PORT = '8181'
- CI_SSL = 'true'
- CI_DELAY = '120'
- CI_DOCKERENV = ''
- CI_AUTH = ''