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

Add support for specifying a path for archive resources #12

Open
waybackarchiver opened this issue Feb 20, 2022 · 4 comments
Open

Add support for specifying a path for archive resources #12

waybackarchiver opened this issue Feb 20, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@waybackarchiver
Copy link
Collaborator

waybackarchiver commented Feb 20, 2022

It is proposed the flag be marked -directory and the short flag -d.

@abhijit-hota
Copy link

abhijit-hota commented May 15, 2022

I believe this is already achieved via the --output option. From the README (emphasis mine):

  • If --output flag is not specified then Obelisk will generate file name for the archive and save it in current working directory.
  • If --output flag is set to - and there is only one URL to process (either from input file or from CLI arguments) then the default output will be stdout.
  • If --output flag is specified but there are more than one URL to process, Obelisk will generate file name for the archive, but keep using the directory from the specified output path.
  • If --output flag is specified but it sets to an existing directory, Obelisk will also generate file name for the archive.

Example usage:

obelisk "https://philipptanlak.com/web-frontends-in-go" --output blogs/go-frontend.html

@waybackarchiver
Copy link
Collaborator Author

I believe this is already achieved via the --output option. From the README (emphasis mine):

  • If --output flag is not specified then Obelisk will generate file name for the archive and save it in current working directory.
  • If --output flag is set to - and there is only one URL to process (either from input file or from CLI arguments) then the default output will be stdout.
  • If --output flag is specified but there are more than one URL to process, Obelisk will generate file name for the archive, but keep using the directory from the specified output path.
  • If --output flag is specified but it sets to an existing directory, Obelisk will also generate file name for the archive.

Example usage:

obelisk "https://philipptanlak.com/web-frontends-in-go" --output blogs/go-frontend.html

You are right. The --output flag is used to archive a single file but separate files with Archiver.WrapDirectory.

@github-actions
Copy link

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions
Copy link

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the Stale label Jan 21, 2023
@fmartingr fmartingr added enhancement New feature or request and removed Stale labels Jan 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants