Downloads:

133

Downloads of v 0.2.2-alpha1:

28

Last Update:

5/4/2019

Package Maintainer(s):

Software Author(s):

  • OpenFlexure

Tags:

openflexure microscope ev

OpenFlexure eV

This is a prerelease version of OpenFlexure eV.

0.2.2-alpha1 | Updated: 5/4/2019

Downloads:

133

Downloads of v 0.2.2-alpha1:

28

Maintainer(s):

Software Author(s):

  • OpenFlexure

OpenFlexure eV 0.2.2-alpha1

This is a prerelease version of OpenFlexure eV.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install OpenFlexure eV, run the following command from the command line or from PowerShell:

>

To upgrade OpenFlexure eV, run the following command from the command line or from PowerShell:

>

To uninstall OpenFlexure eV, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade openflexure-ev -y --source="'STEP 3 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 openflexure-ev -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure openflexure-ev installed
  win_chocolatey:
    name: openflexure-ev
    state: present
    version: 0.2.2-alpha1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'openflexure-ev' do
  action    :install
  version  '0.2.2-alpha1'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: openflexure-ev,
    Version: 0.2.2-alpha1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller openflexure-ev
{
   Name     = 'openflexure-ev'
   Ensure   = 'Present'
   Version  = '0.2.2-alpha1'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'openflexure-ev':
  provider => 'chocolatey',
  ensure   => '0.2.2-alpha1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install openflexure-ev version="0.2.2-alpha1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.
Description

An electron-based user client for the OpenFlexure Microscope Server


tools\chocolateyInstall.ps1
$packageName = 'openflexure-ev'
$fileType = 'exe'
$url = 'https://gitlab.com/openflexure/openflexure-microscope-jsclient/-/jobs/206878608/artifacts/raw/release-builds/OpenFlexure%20eV%20Setup%200.2.2-alpha.1.exe'
$silentArgs = '/S'

Install-ChocolateyPackage $packageName $fileType $silentArgs $url

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.

Version Downloads Last Updated Status
OpenFlexure eV 0.2.6 26 Wednesday, May 29, 2019 Approved
OpenFlexure eV 0.2.3 31 Friday, May 17, 2019 Approved
OpenFlexure eV 0.2.2-alpha2 23 Monday, May 6, 2019 Exempted
OpenFlexure eV 0.2.2-alpha1 28 Saturday, May 4, 2019 Exempted

This package has no dependencies.

Discussion for the OpenFlexure eV Package

Ground Rules:

  • This discussion is only about OpenFlexure eV and the OpenFlexure eV 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 OpenFlexure eV, 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.
comments powered by Disqus