This repository was archived by the owner on Jul 24, 2024. It is now read-only.
  
  
  
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
docker-compose was the better way .
$ git clone https://github.com/forrest419/nx-webxy.git
$ cd nx-webxy
1st way: docker ### run
Replace all the default "site.example.com" and "[email protected]" occurrences in docker-run/simple-site/docker-run.sh for your publicly accessible domain redirecting to the server running the script.
$ ./docker-run.sh
将 docker-run/simple-site/docker-run.sh 中所有示例网域及邮件地址“site.example.com” ,“[email protected]”替换为您解析过可用的公网可访问地址或者重定向到运行脚本的服务器。
运行命令 $ ./docker-run.sh
2nd way: ### docker-compose
While docker-compose v1 file version isn't advised for starting new project, docker-gen hasn't yet officially resolved the issue raised by new networking in docker-compose v2, you might find it easier to stick with v1.
Replace all the default "site.example.com" and "[email protected]" occurrences in docker-compose/v1/simple-site/docker-compose.yml for your publicly accessible domain redirecting to the server running the script.
$ docker-compose up
docker-compose v1文件版本是基础项目版本,但是docker-gen尚未正式解决docker-compose v2中新网络引发的问题,您会发现个人使用v1更简单实用。两个文件的修改方法都只是docker-compose.yml中的所有示例的“site.example.com”和“[email protected]”替换为您解析过,可使用的公网可访问地址,或重定向到运行该脚本的服务器。
$ docker-compose up
v2则需要多一个步骤,创建一个名为'nginx-proxy'的外部网络
$ docker network -d bridge nginx-proxy
你也可以docker-compose文件内的默认网络名称修改为'nginx-proxy'
$ docker-compose up