Java 开源博客 Solo 1.2.0 发布 - 一键启动

@longquanwo Dockerfile 我正在弄了，今天可以完成

@longquanwo 已经弄好了：

docker pull 88250/solo:latest
docker run --net=host 88250/solo:latest java -cp WEB-INF/lib/*:WEB-INF/classes org.b3log.solo.Starter -lp 9090 -sp 9090 -sh public_ip

@88250 哥们，你自己在各大 Docker 镜像中心发布。我们装的多，你的排名就会上升。。

https://hub.alauda.cn

@longquanwo 哦，我是在 Docker 中央库发布的，不知道国内镜像同步的时间。

我们把一些本来要做的配置文件都做成命令行参数了，希望能有更多的小伙伴能够体验！

想问一下，是如何做到 #345 后就是 #11755 的……中间 11409 个 issue 到哪儿去了？！

@88250 https://hub.docker.com/r/88250/solo/ 这个是你发布的吗

@88250 https://hub.alauda.cn/repos/bitswrt/solo

我帮你分享了，如有意见，我立马删掉

@88250 我正在构建版本，完事后，这才叫一键安装、启动、迭代。。。。。。

2015-12-05 17:49:58 [INFO] Final Memory: 7M/57M



2015-12-05 17:49:58 [INFO] ------------------------------------------------------------------------



2015-12-05 17:49:58 [ERROR] Plugin org.apache.maven.plugins:maven-resources-plugin:2.7 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.7: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.7 from/to central ( http://repo1.maven.org/maven2): Connect to repo1.maven.org:80 [repo1.maven.org/199.27.79.209] failed: Connection timed out -> [Help 1]



2015-12-05 17:49:58 [ERROR]



2015-12-05 17:49:58 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.



2015-12-05 17:49:58 [ERROR] Re-run Maven using the -X switch to enable full debug logging.



2015-12-05 17:49:58 [ERROR]



2015-12-05 17:49:58 [ERROR] For more information about the errors and possible solutions, please read the following articles:



2015-12-05 17:49:58 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException



2015-12-05 17:49:59 Removing intermediate container 1a7e7b7ba595



2015-12-05 17:49:59 time="2015-12-05T09:49:59Z" level=info msg="The command [/bin/sh -c mvn install] returned a non-zero code: 1"



2015-12-05 17:49:59 Build failed! Please check errors in the log. If you need help, please cut a ticket to us

@orzfly 以前被攻击过，有人发了很多垃圾信息，我报告 GitHub 后他们帮忙删除了

@longquanwo 现在还是构建不过去么？

歪个楼，如果你用 go 开发，我觉得才是最容易跑起来的博客

@julor 嗯，也有考虑过用 Golang 再写一版。目前最大的问题是模版引擎， Solo 用的是 FreeMarker ，如果用 Golang ，模版不打算动，这就需要有个 Golang 版的 FreeMarker 了....