search

codingteam / codingteam.org.ru

Our main web site.
https://codingteam.org.ru
MIT License
2 stars 1 forks source link

Robust deployment system #5

Closed ForNeVeR closed 9 years ago

ForNeVeR commented 10 years ago

I think we should give sbt-native-packager a try. So our orchestra will need two distinct machines:

  1. Package builder (we are free to use CI here).
  2. Production server (with deb package system, for example).

Package builder machine is the one who constantly monitors git repository (again - we're free to use server-side github hooks or any other known hookers to make the work). It will build the packages and deploy them into repository.

Production server should monitor only our deb repository (only Omnissiah knows how to maintain that sort of thing, but I hope Emperor will guide us) and auto-update the package from it.

Personally I'd propose using the Windows service for maintaining the repository (exclusively for the purpose of maximal fun). I had some thoughts about using Apache Commons Daemon for managing the service.

ForNeVeR commented 9 years ago

Well, now all deployment is managed by jenkins and vagrant and I don't think we currently want something else.