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.
This is a small improvement for the copy tasks in the static directories
As the role currently works, the whole static directory is
rsync
ed into every new subdomain directory, which leads to additional disk usage of ~ 154 MB for each subdomain in a basic (GTN) Galaxy setup.With this improvement, several static subdirectories are symlinked and all files inside
dist
are symlinked, which reduces the disk usage per subdomain to ~ 2.3 MB.However the disadvantage of this is:
galaxy_themes_no_symlink_logs
just reduces the extent, but ansible still prints one line per file and subdomainsynchronize
for the whole folder is faster than invoking an ansible operation for each file and we don't get rid of thesynchronize
fully, because we would need to create multiple subdirectories manually and iterate over them with symlink tasksTo solve this conflict, I added variables that let the user decide weather to use the symlink feature and reduce the logs or not