Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • W website
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • kwantkwant
  • website
  • Issues
  • #6
Closed
Open
Issue created Nov 26, 2015 by Anton Akhmerov@anton-akhmerovOwner5 of 7 checklist items completed5/7 checklist items

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?

Assignee
Assign to
Time tracking