Just need the syntax for v3 cli [again] #578
Unanswered
ianbmacdonald
asked this question in
Q&A
Replies: 2 comments 5 replies
-
|
Hey @ianbmacdonald, The equivalent command would be: Note, that with v3.1+ you might be better off with the archive format: It generates a sqlite database. Afterwards, you can convert it to standard export any time should it be required: Happy dumping :) |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Also, thanks for your support! |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
It seems I have overflowed my bash history since the last time I ran v3 on the cli (3.1.8 deb). For the life of me I seem to be having trouble reproducing my normal command to dump my workspace.
Authentication type (please read)
Using my provider.bin
To Reproduce
slackdump export helpto figure out the equivalent of the v2 command (possibly earlier) below, but failingslackdump -f -export 251212_workspacebackup.zip -export-type standardExpected behavior
Figure it out from cli help, man page, personal wiki or bash history.
Output
Desktop (please complete the following information):
ii slackdump 3.1.10-1 amd64Additional context
Looked in these places
https://github.com/rusq/slackdump
https://github.com/rusq/slackdump/blob/master/doc/usage-export.rst
https://github.com/rusq/slackdump/blob/071df512ac89c07402e4e03ef321b70e4d0174da/cmd/slackdump/internal/man/assets/v2migr.md
https://github.com/rusq/slackdump/blob/071df512ac89c07402e4e03ef321b70e4d0174da/cmd/slackdump/internal/man/assets/changelog.md
I also tried the wizard, and it just gets stuck at
Run Wizard->Exportjust returning to the highlighted menu option when I select it.I prefer the programatic swapping of bins on the cli.
Yawn. I am a bit tired, but this seems a lot harder to re-figure out than it should be. I blame Claude for the .bash_history overflow, but even still.
Super tool, definately worth the coffee I plan to have.
Beta Was this translation helpful? Give feedback.
All reactions