This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
Starts the service after redis #12
Merged
Conversation
This file contains 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
4 tasks
kushaldas
force-pushed
the
start_after_redis
branch
from
0163793
to
a9a02ea
Compare
emkll
approved these changes
Feb 11, 2020
There was a problem hiding this comment.
@kushaldas I've tested the changes locally as follows:
I have built a package from this branch and installed the package in securedrop-log-buster-template, and the logs are still flowing through to sd-log after a reboot. Combined with a visual diff review, I think this is fine to merge in order to unblock work #447.
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.
Starts the
securedrop-logservice only after theredisservice is running.This is something I found while working on freedomofpress/securedrop-workstation#447