Downloads:
1,302
Downloads of v 2.1.17:
913
Last Update:
01 Feb 2017
Package Maintainer(s):
Software Author(s):
- getpocket.com
Tags:
pocket chrome extension- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Save to Pocket for Chrome
- 1
- 2
- 3
2.1.17 | Updated: 01 Feb 2017
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,302
Downloads of v 2.1.17:
913
Maintainer(s):
Software Author(s):
- getpocket.com
Save to Pocket for Chrome 2.1.17
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by getpocket.com. The inclusion of getpocket.com trademark(s), if any, upon this webpage is solely to identify getpocket.com goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Save to Pocket for Chrome, run the following command from the command line or from PowerShell:
To upgrade Save to Pocket for Chrome, run the following command from the command line or from PowerShell:
To uninstall Save to Pocket for Chrome, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download save-to-pocket-chrome --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade save-to-pocket-chrome -y --source="'INTERNAL REPO URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade save-to-pocket-chrome -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install save-to-pocket-chrome
win_chocolatey:
name: save-to-pocket-chrome
version: '2.1.17'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'save-to-pocket-chrome' do
action :install
source 'INTERNAL REPO URL'
version '2.1.17'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller save-to-pocket-chrome
{
Name = "save-to-pocket-chrome"
Version = "2.1.17"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'save-to-pocket-chrome':
ensure => '2.1.17',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator AdmiringWorm on 01 Feb 2017.
Pocket Extension for Chrome - The best way to save articles, videos and more
When you find something in Chrome that you want to view later, put it in Pocket. It automatically syncs to your phone, tablet or computer so you can view it at any time, even without an internet connection.
Extension Features:
- One-click saving of any page with the toolbar button or keyboard shortcut
- Right-click menu item to save any link, no need to load the page first
- Quickly add tags
- See related recommendations when you save to Pocket
- See trending stories and topics when you open a new tab
- Syncs across all devices – iPhone, iPad, Android and more
- Completely free, upgrade anytime to Premium for a more powerful Pocket experience
Get the Pocket App to see all the great things you’ve saved to Pocket! https://chrome.google.com/webstore/detail/jijgclgmgjipgefcnnnibgllfonlfdap
PACKAGING NOTE: This installs no software. It installs a registry key for the extension that Chrome will see and then ask you for permission to enable the extension if you are in Chrome or on the next run. Chrome will install the latest version of the extension. The mentioned version is the version at time of packaging, you can ignore it. Chrome will handle updates to the extension.
$bits = Get-ProcessorBits
$packageName = 'save-to-pocket-chrome'
$extensionID = 'niloccemoadcdkdjlinkgdfekeahmflj'
if ($bits -eq 64) {
Remove-Item "HKLM:\SOFTWARE\Wow6432node\Google\Chrome\Extensions\$extensionID" -Force -ErrorAction SilentlyContinue | out-null
}else{
Remove-Item "HKLM:\SOFTWARE\Google\Chrome\Extensions\$extensionID" -Force -ErrorAction SilentlyContinue | out-null
}
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Save to Pocket for Chrome 2.1.17 | 913 | Wednesday, February 1, 2017 | Approved | |
Save to Pocket for Chrome 2.1.11 | 389 | Monday, November 7, 2016 | Approved |
getpocket.com
updated to new install method
Ground Rules:
- This discussion is only about Save to Pocket for Chrome and the Save to Pocket for Chrome package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Save to Pocket for Chrome, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.