Sitecore：为多站点设置Solr核心的最佳实践(Sitecore: Best practices for setting up Solr core for multisite)

 我推荐Travis CI + Heroku 。 
 
 您只需使用git push就可以直接部署到heroku，但我希望在此之前使用Travis构建并运行测试。 
 
 网上有一些指南，但我会尝试直接指向： 
 
 你需要什么？ 
 
 
 
 Github帐号 
 
 
 Travis帐户（与github链接，如果是开源免费） 
 
 
 空Heroku应用程序（免费dyno工作很棒） 
 
 
 建立 
 
 在您的github仓库中，创建以下文件： 
 
 
 
 .travis.yml（有关Travis CI文档的更多信息） 
 
 
 Procfile 
 
 
 。去-DIR 
 
 
 之后转到Travis帐户，添加您的存储库并为其启用构建。 
 
 这是一个示例最小配置文件内容（基于我部署到heroku的应用程序）： 
 
 .travis.yml 
 
language: go
go:
  - tip
deploy:
  provider: heroku
  buildpack: https://github.com/kr/heroku-buildpack-go.git
  api_key:
    secure: <your heroku api key encripted with travis encrypt>
  on: master 
 
 Procfile 
 
worker: your-app-binary
 
 。去-DIR 
 
your-app-binary
 
 Procfile和.go-dir是heroku配置，所以如果你正在部署一个web应用程序它会有所不同，你可以在heroku文档中阅读更多内容 
 
 一个重要且容易遗漏的点是构建包 ，没有它，部署将无法工作。 
 
 阅读Travis文档，了解如何加密heroku密钥 
 
 怎么运行的？ 
 
 基本上，每次推送到您的存储库都会触发Travis CI构建，如果它通过它会将应用程序部署到heroku，所以你设置一次，构建+部署只是一个推动;） 
 
 此外，Travis将自动构建并更新所有Pull请求的状态到您的存储库。 
 
 要查看我的配置和构建，请使用我的工作配置查看我的Travis构建和我的存储库 

I recommend Travis CI + Heroku.
 
You can deploy to heroku directly with just a git push, but I like to use Travis to build and run the tests before that.
 
There are some guides online but I'll try to go directly to the point:
 
What you will need?
 
 
 
Github account
 
 
Travis account (linked with github, free if open source)
 
 
Empty Heroku app (Free dyno works great)
 
 
Setup
 
In your github repo, create the following files:
 
 
 
.travis.yml (more info on the Travis CI documentation)
 
 
Procfile
 
 
.go-dir
 
 
After that go to your Travis account, add your repository and enabled the build for it.
 
Here is a sample minimal config file content (based on my app that I deploy to heroku):
 
.travis.yml
 
language: go
go:
  - tip
deploy:
  provider: heroku
  buildpack: https://github.com/kr/heroku-buildpack-go.git
  api_key:
    secure: <your heroku api key encripted with travis encrypt>
  on: master 
 
Procfile
 
worker: your-app-binary
 
.go-dir
 
your-app-binary
 
Procfile and .go-dir are heroku configs so it can vary if you are deploying a web app, you can read more at the heroku documentation
 
One important and easily missed point is the build pack, without it the deploy will not work.
 
Read the Travis docs to see how to encrypt the heroku key
 
How it works?
 
Basically, every push to your repository will trigger the Travis CI build, if it passes it will deploy the app to heroku, so you set this up once and build + deploy is just a push away ;)
 
Also Travis will build and updated the status of all Pull Requests to your repository automagically.
 
To see my config and build, please take a look at my Travis build and my repository with my working configs