CI & auto-deploy

Plan:

• set up a test deployment location at test.kwant-project.org.
• set up restricted rsync users with passwordless keys that can only copy to
  • Test website
  • Actual website
• set up CI to build the website and deploy
  • To test location on any push
  • To the main location on pushes to master

The keys can be stored on the computer providing runners and mounted at .ssh/id_rsa as volumes. The runner for the test location may or may not be shared with other website users (mildly prone to abuse). @cwg, @jbweston – opinion about this last point?

@cwg the test location doesn't support .svgz, can you please check the server settings?

Anton Akhmerov wrote:

@cwg the test location doesn't support .svgz, can you please check the server settings?

SVGZ-Support is enabled in ".htaccess" that got deleted somehow.

Ah, that's my bad, I just didn't copy it :-)

The keys can be stored on the computer providing runners and mounted at .ssh/id_rsa as volumes. The runner for the test location may or may not be shared with other website users (mildly prone to abuse).

Does this mean that anyone who registers an account can use the runner and recover the private key? Then I think that it’s not a good idea.

Also as there wouldn’t be anymore a single list of builds it would be difficult to see what the test website actually is showing.

You're correct in the interpretation. We could think of more intricate schemes of moving the output from the runner to the website, but the scheme we're considering now would necessarily have this drawback.

Everything except the deploy on pushes to master is implemented in !5 (merged)

mentioned in commit bd556546

mentioned in merge request !9 (merged)

Status changed to closed by commit bd556546