This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

Copyright (c) 2010-2015 gocept gmbh & co. kg

All Rights Reserved.

This software is subject to the provisions of the Zope Public License, Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution. THIS SOFTWARE IS PROVIDED “AS IS” AND ANY AND ALL EXPRESS OR IMPLIED WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Custom egg upload

This package provides a plugin for zest.releaser that offers to upload the released egg via SCP, SFTP or HTTP(S) PUT (WebDAV) to a custom location (instead of or in addition to PyPI).

To use, add a section to your ~/.pypirc like the following:

[gocept.zestreleaser.customupload]
gocept = scp://download.gocept.com//var/www/packages
gocept.special = http://dav.gocept.com/special
gocept.sftp = sftp://repo@repo.gocept.com/home/repo/eggs

If the name of the package being released starts with one of the keys in that section (longest match wins, case insensitive), you will be prompted whether to upload the egg (that was created by zest.releaser by checking out the tag) to the given server.

Options for HTTP(S) PUT (WebDAV)

HTTP(S) PUT (WebDAV) is implemented using curl to add options to curl, e. g. to disable certificate checks, add the options in front of the URL like this:

[gocept.zestreleaser.customupload]
gocept.special = --insecure https://dav.gocept.com/special

Uploading Documentation

In addition to uploading the egg, the plugin also offers to upload generated documentation.

To use this functionality, create a ~/.zestreleaserrc that contains something like the following:

[gocept.zestreleaser.customupload.doc]
gocept = docs.gocept.com:/var/www/doc

If the name of the package being released starts with one of the keys in that section, the plugin will run ./bin/doc to generate the documentation and then prompt to upload the contents of ./build/doc. The upload destination is assembled from the configured prefix, the package name and version. In the example, the upload location would be /var/www/doc/gocept.foo/1.3.

Development

The source code is available in the Mercurial repository at https://bitbucket.org/gocept/gocept.zestreleaser.customupload

Please report any bugs you find at https://bitbucket.org/gocept/gocept.zestreleaser.customupload/issues

Changelog

2.0 (2015-11-18)

1.4 (2012-07-31)

  • If the destination URL contains username and password, do not display the password on the console when asking for upload.
  • Allow options in HTTP(S) PUT (WebDAV) upload.
  • Added some trove classifiers to indicate suported Python versions.

1.3 (2012-05-15)

1.2.1 (2012-05-07)

  • Fixed documentation of SCP upload configuration.

1.2 (2012-01-20)

  • Add second plugin point that builds and uploads documentation

1.1.0 (2011-11-18)

  • Allow uploading via HTTP PUT (WebDAV) [CZ].

1.0.3 (2011-11-11)

1.0.2 (2010-07-22)

  • Upload everything from the dist/ directory, so it works for any egg format, .zip, .tar.gz, .egg, or else [suggestion by maurits@vanrees.org].

1.0.1 (2010-07-22)

  • Added a MANIFEST.in so that the created egg actually works.

1.0 (2010-07-22)

  • first release [WS].
Release History

Release History

2.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.2.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.1.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
gocept.zestreleaser.customupload-2.0.tar.gz (13.3 kB) Copy SHA256 Checksum SHA256 Source Nov 18, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting