Skip to content

Changed tar exclude to be the configured dir#1508

Merged
dgibbs64 merged 1 commit intoGameServerManagers:developfrom
Drizzt321:master
Jul 10, 2017
Merged

Changed tar exclude to be the configured dir#1508
dgibbs64 merged 1 commit intoGameServerManagers:developfrom
Drizzt321:master

Conversation

@Drizzt321
Copy link
Copy Markdown
Contributor

Updated the tar exclude to be the configured backup dir, instead of just a hardcoded "backup". This allows for people to change the backup directory location to still be in the game server dir, but in a custom directory. For me specifically it's an NFS mounted directory to backup to my NAS with the cloud backup then enabled on that dir.

Updated the tar exclude to be the configured backup dir, instead of just a hardcoded "backup". This allows for people to change the backup directory location to still be in the game server dir, but in a custom directory. For me specifically it's an NFS mounted directory to backup to my NAS with the cloud backup then enabled on that dir.
@Drizzt321
Copy link
Copy Markdown
Contributor Author

Strange. If I'm reading it right the test scripts were having trouble simply fetching https://raw.githubusercontent.com/GameServerManagers/LinuxGSM/master/lgsm/functions/core_dl.sh? So it's not a problem with my PR?

@UltimateByte
Copy link
Copy Markdown
Contributor

Don't worry about Travis test, it's fixed in the dev branch :)

@Drizzt321
Copy link
Copy Markdown
Contributor Author

Ha! Ok :) I'm also going to do some comparisons with bzip2 vs gzip, and various compression options to see about time and output file size if there's much of a difference. Not in this PR though.

@UltimateByte
Copy link
Copy Markdown
Contributor

Excellent idea :)

@dgibbs64 dgibbs64 changed the base branch from master to develop July 10, 2017 15:31
@dgibbs64 dgibbs64 merged commit c324e9d into GameServerManagers:develop Jul 10, 2017
@lock
Copy link
Copy Markdown

lock Bot commented Jul 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock Bot locked as resolved and limited conversation to collaborators Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants