This repository was archived by the owner on Feb 18, 2025. It is now read-only.
Merged
Conversation
… create the appropriate symlink
…rvice' in systemd unit file
shlomi-noach
approved these changes
Dec 4, 2019
Collaborator
shlomi-noach
left a comment
There was a problem hiding this comment.
I'm sorry for the delay
shlomi-noach
suggested changes
Dec 4, 2019
Collaborator
shlomi-noach
left a comment
There was a problem hiding this comment.
small change requested in docs
Explain that the chapter is only for MySQL Backend as opposed to SQLite Co-Authored-By: Shlomi Noach <shlomi-noach@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow up of discussion in #653
Description
This PR propose to add a systemd target in systemd unit file. This will allow the command
systemctl enableto create the appropriate symlink.Additionally, in case the backend is MySQL, document how to tell Orchestrator to boot after MySQL. This ensure that Orchestrator starts each time without error "FATAL dial tcp 127.0.0.1:3306: connect: connection refused orchestrator.service failed"