Install original Neko Chromium extensions at container runtime #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Aaron <[email protected]>
|
@WhaleHub how is that loading extensions? You are expecting them in |
Signed-off-by: Aaron <[email protected]>
wanjohiryan
referenced
this pull request
in wanjohiryan/Arc3dia
Nov 16, 2022
wanjohiryan
referenced
this pull request
in wanjohiryan/Arc3dia
Nov 16, 2022
m1k1o
added a commit
that referenced
this pull request
Jun 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@m1k1o A little background info for this pull request: The custom Chromium build which I added support for in #1 is commonly called "Ungoogled Chromium" because it is compiled without support for Google components like the Chrome Web Store. This is why uBlock Origin and NordVPN, the two extensions which are automatically installed in the original Neko image, could not be automatically installed from the Chrome Web Store after we replaced the default Chromium build and have been missing from this Neko fork ever since.
This pull request adds support for automatically installing those two extensions at container runtime through the use of External Extension Descriptors.