160 remove start aaecsh script #222
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
|
This version has been successfully deployed to the libappstest server |
crowesn
approved these changes
Oct 3, 2023
|
@Janell-Huyck I can merge this after the Gemfile.lock conflict is resolved. |
Janell-Huyck
force-pushed
the
160-remove-start-aaecsh-script
branch
from
5c2ab2d to
d79e4a7
Compare
|
rebased and fixed merge conflict |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #160
Removes the script "start-aaec.sh".
This script was used when we were running Puma as a daemon service. It was used to restart the Puma service. Since we are now running Puma as a service controlled by systemctl, the script is no longer being used.