Complete rework and update of JPS #6
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
Here is the complete rework of this JPS:
Changes:
Added a beforeinstall.js file that defines the nodes depending on users selection.
Added option of using litespeed or apache and dedicated storage or storage cluster
activated built-in SSL by default
enabled system cron by default for owncloud
enabled and added redis configuration to owncloud
Split out text for success message into dedicated files
Separate messages for e-mail and direct text with individual infos
set appropriate cloudlets for idle load
I tested it on the infomaniak platform but not on other ones and for me it worked well :)
Let me know if you have any comments or questions