/ 
App-FirefoxMultiAccountContainersUtils-0.018
River stage one • 1 direct dependent • 1 total dependent
/ open-firefox-container

NAME

open-firefox-container - CLI to open URL in a new Firefox tab, in a specific multi-account container

VERSION

This document describes version 0.018 of open-firefox-container (from Perl distribution App-FirefoxMultiAccountContainersUtils), released on 2024-10-01.

SYNOPSIS

open-firefox-container --help (or -h, -?)

open-firefox-container --version (or -v)

open-firefox-container [--debug|--log-level=level|--quiet|--trace|--verbose] [(--extra-firefox-options-after=str)+|--extra-firefox-options-after-json=json|(-a=str)+] [(--extra-firefox-options-before=str)+|--extra-firefox-options-before-json=json|(-b=str)+] [--format=name|--json] [--(no)naked-res] [--page-result[=program]|--view-result[=program]] [--profile=firefox::local_profile_name::default_first] [(--url=str)+|--urls-json=json] -- <container> [url] ...

See examples in the "EXAMPLES" section.

DESCRIPTION

This utility opens a new firefox tab in a specific multi-account container. This requires the Firefox Multi-Account Containers add-on, as well as another add-on called "Open external links in a container", https://addons.mozilla.org/en-US/firefox/addon/open-url-in-container/.

The way it works, because add-ons currently do not have hooks to the CLI, is via a custom protocol handler. For example, if you want to open http://www.example.com/ in a container called mycontainer, you ask Firefox to open this URL:

ext+container:name=mycontainer&url=http://www.example.com/

Ref: https://github.com/mozilla/multi-account-containers/issues/365

Related topics

In Google Chrome browser, profiles is what you would use to separate sessions/cookies (and other things). Opening a URL in a specific profile from the command-line is easier with Chrome:

% google-chrome --profile-directory="PROFILEDIRNAME" URL

where PROFILEDIRNAME is a directory name under the profiles directory, typically ~/.config/google-chrome/ on Unix. You can use the list-chrome-profiles (with option -l) (from App::ChromeUtils) to list Chrome profiles.

OPTIONS

* marks required options.

Main options

--container=s*

(No description)

Can also be specified as the 1st command-line argument.

--extra-firefox-options-after-json=s, -a

Additional options (arguments) to put after the URLs (JSON-encoded).

See --extra-firefox-options-after.

--extra-firefox-options-after=s@

Additional options (arguments) to put after the URLs.

Can be specified multiple times.

--extra-firefox-options-before-json=s, -b

Additional options (arguments) to put before the URLs (JSON-encoded).

See --extra-firefox-options-before.

--extra-firefox-options-before=s@

Additional options (arguments) to put before the URLs.

Can be specified multiple times.

--profile=s

(No description)

--url=s@

(No description)

Can also be specified as the 2nd command-line argument and onwards.

Can be specified multiple times.

--urls-json=s

See --url.

Can also be specified as the 2nd command-line argument and onwards.

Logging options

--debug

Shortcut for --log-level=debug.

--log-level=s

Set log level.

By default, these log levels are available (in order of increasing level of importance, from least important to most): trace, debug, info, warn/warning, error, fatal. By default, the level is usually set to warn, which means that log statements with level info and less important levels will not be shown. To increase verbosity, choose info, debug, or trace.

For more details on log level and logging, as well as how new logging levels can be defined or existing ones modified, see Log::ger.

--quiet

Shortcut for --log-level=error.

--trace

Shortcut for --log-level=trace.

--verbose

Shortcut for --log-level=info.

Output options

--format=s

Choose output format, e.g. json, text.

Default value:

undef

Output can be displayed in multiple formats, and a suitable default format is chosen depending on the application and/or whether output destination is interactive terminal (i.e. whether output is piped). This option specifically chooses an output format.

--json

Set output format to json.

--naked-res

When outputing as JSON, strip result envelope.

Default value:

0

By default, when outputing as JSON, the full enveloped result is returned, e.g.:

[200,"OK",[1,2,3],{"func.extra"=>4}]

The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use --naked-res so you just get:

[1,2,3]
--page-result

Filter output through a pager.

This option will pipe the output to a specified pager program. If pager program is not specified, a suitable default e.g. less is chosen.

--view-result

View output using a viewer.

This option will first save the output to a temporary file, then open a viewer program to view the temporary file. If a viewer program is not chosen, a suitable default, e.g. the browser, is chosen.

Other options

--help, -h, -?

Display help message and exit.

--version, -v

Display program's version and exit.

COMPLETION

This script has shell tab completion capability with support for several shells.

bash

To activate bash completion for this script, put:

complete -C open-firefox-container open-firefox-container

in your bash startup (e.g. ~/.bashrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.

It is recommended, however, that you install modules using cpanm-shcompgen which can activate shell completion for scripts immediately.

tcsh

To activate tcsh completion for this script, put:

complete open-firefox-container 'p/*/`open-firefox-container`/'

in your tcsh startup (e.g. ~/.tcshrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.

It is also recommended to install shcompgen (see above).

other shells

For fish and zsh, install shcompgen as described above.

EXAMPLES

Open two URLs in a container called "mycontainer"

% open-firefox-container mycontainer www.example.com www.example.com/url2

If URL is not specified, will open a blank tab

% open-firefox-container mycontainer

Open URL in a new tab in a new window

% open-firefox-container mycontainer www.example.com -b --new-window

This command passes the --new-window option to firefox.

HOMEPAGE

Please visit the project's homepage at https://metacpan.org/release/App-FirefoxMultiAccountContainersUtils.

SOURCE

Source repository is at https://github.com/perlancar/perl-App-FirefoxMultiAccountContainersUtils.

SEE ALSO

open-browser.

AUTHOR

perlancar <perlancar@cpan.org>

CONTRIBUTING

To contribute, you can send patches by email/via RT, or send pull requests on GitHub.

Most of the time, you don't need to build the distribution yourself. You can simply modify the code, then test via:

% prove -l

If you want to build the distribution (e.g. to try to install it locally on your system), you can install Dist::Zilla, Dist::Zilla::PluginBundle::Author::PERLANCAR, Pod::Weaver::PluginBundle::Author::PERLANCAR, and sometimes one or two other Dist::Zilla- and/or Pod::Weaver plugins. Any additional steps required beyond that are considered a bug and can be reported to me.

COPYRIGHT AND LICENSE

This software is copyright (c) 2024, 2023, 2022, 2020 by perlancar <perlancar@cpan.org>.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

BUGS

Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-FirefoxMultiAccountContainersUtils

When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.