Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mention that tar can be used as an alternative #72

Open
Mossman1215 opened this issue Feb 12, 2019 · 3 comments
Open

mention that tar can be used as an alternative #72

Mossman1215 opened this issue Feb 12, 2019 · 3 comments

Comments

@Mossman1215
Copy link

silverstripe platform requires using sspak but sspak never mentions how to use gnu tar to create archives instead which is the recommended approach from ops for production level assets and database snapshots. sspak often fails
https://www.cwp.govt.nz/service-desk/requests/desk/view.php?id=35475

@robbieaverill
Copy link
Contributor

Can you please clarify this request a little @Mossman1215? Also if you could post the relevant parts of that link here that'd be cool - not everyone has access to it =)

@Mossman1215
Copy link
Author

Summary of the conversation:

| I am trying to create and download a snapshot of the assets from the moetec site. The dashboard > appears to create a sspak file correctly, although it is over 5GB. After downloading the file it reports it > as corrupted every time an extraction is tried.

Hi MOss,
This is all happening on Ubuntu 18.04 - does the initial "sspak -extract [file]" command use gnu tar? It > is during this command that we are encountering the issue.

Oh don't use sspak !
it literally never works with production level assets and tends to create broken tar packages.
use tar -xvf on the sspack instead an you're going to have better luck.

Cheers,
Moss

Right well that worked - there is no mention of using tar in the CWP documentation or the SSPAK documentation by the way.

So I'm wondering where to mention a bypass if sspak is failing for devs

@robbieaverill
Copy link
Contributor

Related: #29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants