Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5] Setup deployment of cepta on server #37

Open
5 of 10 tasks
skydivin4ng3l opened this issue Nov 12, 2019 · 2 comments
Open
5 of 10 tasks

[5] Setup deployment of cepta on server #37

skydivin4ng3l opened this issue Nov 12, 2019 · 2 comments
Assignees

Comments

@skydivin4ng3l
Copy link
Contributor

skydivin4ng3l commented Nov 12, 2019

As a

Product Owner

I want

to always see the current state of master branch on the "live" server

Because

I want to review all tasks on the live server

Prerequisite

Tasks

  • get access from the admins (asks Stephan/Sven for contact info)
  • receive the Introduction from admins
  • write docker compose file for production
  • connect to vm and setup jenkins for own purpose
  • setup cepta for deployment after each push to master

Acceptance Criteria

  • Documented
  • on Master
  • Reviewed by PO
@skydivin4ng3l skydivin4ng3l changed the title [Not estimated yet] deploy on server [Not estimated yet] Setup deployment of cepta on server Nov 12, 2019
@skydivin4ng3l
Copy link
Contributor Author

replaces #6

@skydivin4ng3l skydivin4ng3l changed the title [Not estimated yet] Setup deployment of cepta on server [5] Setup deployment of cepta on server Nov 19, 2019
@romnn romnn self-assigned this Nov 19, 2019
@leopetter leopetter self-assigned this Nov 19, 2019
@romnn romnn mentioned this issue Dec 5, 2019
12 tasks
@leopetter
Copy link
Contributor

We have access to the server via our VM and are able to configure our production deployment.

@romnn romnn removed their assignment May 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants