semvec/pypi-packages huggingface dataset:
galaxyservers 0.1.1
Runners for Galaxyproject
License: MIT

Galaxyservers
=============

This package is a release supporting the poster presentation at GCC2013/Oslo.
The work is still in progres, we will incremently add servers and installation
instructions to this package.

Installation
--------------

To install this package you will need either root access or preferabel install into
your virtualenv. 

### Installation of WSGI-servers

Some of the WSGI-server require supplementary installation of supporting software/libraries.

One common package to install is **python-dev**, this can be installed by:

    sudo apt-get install python-dev build-essential

On Debian/Ubuntu based systems.

#### Fapws3
In order to install Fapws3, you need to install 1 system package called 'libev'. This packages handles the event-based system calls.

    sudo apt-get install libev libev-dev

Inside your virtualenv, installation of Fapws3 is done by:

    pip install fapws3

Thats all! Once installed, proceed with configuring your Galaxy instance

#### Gunicorn

Installation of Gunicorn also requires the installation of the **python-dev** library headers. Install the following into your virtualenv: (or even system-wide)

    pip install greenlet gunicorn

That's all!

#### Tornado

    pip install tornado

#### uWSGI

    pip install uwsgi

### Configuring your Galaxy instance

Open **universe_wsgi.ini** and search for the following section:

    [server:main]
    use = egg:Paste#http

You can replace the **egg:Paste#http** by any server supported by this package:

    [server:main]
    use = egg:galaxyservers#gunicorn
	# you can replace gunicorn by: fapws3/tornado

##### one exception
uWSGI requires a slightly different setup.
django-storelocator 0.1
Django Storelocator is a Django App for locating stores near a geographical location.
License: MIT

Django Store Locator
        ====================
        
        Django Storelocator is a Django App for locating stores near a geographical location.
        
        The documentation of Django Storelocator can be
        found on `django-storelocator.readthedocs.org <https://django-storelocator.readthedocs.org>`_
redmine-releasedate 0.1.2
Track when your features are shipped to production in Redmine.
License: MIT

Redmine releasedate
===================

Track when your features are shipped to production in Redmine.
Currently supports git & jenkins.

.. image:: https://travis-ci.org/futurecolors/redmine-releasedate.png?branch=master
    :target: https://travis-ci.org/futurecolors/redmine-releasedate

.. image:: https://coveralls.io/repos/futurecolors/redmine-releasedate/badge.png?branch=master
    :target: https://coveralls.io/r/futurecolors/redmine-releasedate

.. image:: https://pypip.in/v/redmine-releasedate/badge.png
    :target: https://crate.io/packages/redmine-releasedate/

How it works
------------

Upon finishing deploy job, jenkins creates a git tag, so it can track commits that refer to the build.
We can use these tags to track which tickets were deployed.
Date of deploy is stored in custom field of each ticket that was mentioned in commit.
A comment is left for every ticket in release as well for readability.

Installation
------------

Server
~~~~~~

Install it where your git repo resides. We only support local git repos, so make sure you have enough permissions.

* ``pip install redmine-releasedate``
* Specify redmine access options in ``releasedate.cfg``
* run ``redmine-release-server`` and make it available via http
::

    # releasedate.cfg
    [redmine]
    url = http://example.com
    token = your_api_token_goes_here
    released_at_id = 42  ;custom field id goes here

    [releasedate]
    message = Deployed on %(instance)s at %(date)s in release "%(release_id)s":%(release_url)s
    address = 0.0.0.0  ; optional
    port = 8080  ; optional


Jenkins
~~~~~~~

* Pip install ``redmine-releasedate`` on your jenkins server. No configuration is needed.

* Add this to your Jenkins build step (preferably, in `post-build task`_)::

    git push --tags
    redmine-release http://releasedate_url/ /path/to/repo/ [instance_url]


.. _post-build task: https://wiki.jenkins-ci.org/display/JENKINS/Post+build+task


Redmine
~~~~~~~

Create a user with permissions to edit tickets and post notes in your project.
Obtain his API token and put it into ``releasedate.cfg``.
Add custom field to store releasedate information.


Limitations
-----------
* second run of client command will make second comment and overwrite release date, so please make sure
you run ``redmine-release`` only once per deploy.


See also
--------

* `Redmine hudson plugin`_
* `Jenkins redmine plugin`_

.. _Redmine hudson plugin: http://www.r-labs.org/projects/r-labs/wiki/Hudson_En
.. _Jenkins redmine plugin: https://wiki.jenkins-ci.org/display/JENKINS/Redmine+Plugin


Changelog
=========

0.1.2 (01-07-2013)
------------------
* Fixed setup.py

0.1.1 (01-07-2013)
-----------------
* Added 3rd optional ``instance_url`` argument to ``redmine-release`` command
* Fixed redmine-release-server cli command
* Fixed unicode message handling in config
* Improved logging

0.1 (01-07-2013)
----------------
* Initial release
corrections 0.2.3
UNKNOWN
License: MIT
Keywords: twitter bot corrections

corrections
===========

An extendable Python based Twitter bot which will reply to various keyworded tweets.

*"Isn't this against the ToS?"*, I hear you ask. Well, sort of, but sort of not. Yes, it might be covered by the *spamming* or *unsolicited mentions* rules, but in my opinion, no more than some asshole going around correcting people manually, depending on your settings.

Example usage
-------------
Here's my favourite use of the Corrections bot (and why I actually wrote this): the **a lot** correction bot:

.. code-block:: python

    # -*- coding: utf-8 -*-
    from corrections import Correct
    from random import choice

    class Alot(Correct):
        auth = (OAUTH_TOKEN,
                OAUTH_SECRET,
                CONSUMER_KEY,
                CONSUMER_SECRET)
        phrases = ["alot"]
        cooldown = (60 * 5, 60 * 3)

        def reply(self, phrase, user):
            return choice([
                "@{user}: a lot*",
                "@{user}: Surely you mean 'a lot', right?",
                "@{user}: I think you meant 'a lot'!",
                "@{user}: Come on, use 'a lot', lazy..",
                "@{user}: Alot is sad you can't use 'a lot' right..",
                "@{user}: There should be a space in there somewhere.. 'a lot'*",
            ]).format(user=user)

    if __name__ == "__main__":
        correct = Alot()
        correct()

Just for testing
----------------
Want to make sure your bot is functional but don't want to start spamming tweets yet?
Easy! Set `dry = True` in your Corrections class and Corrections won't actually update your status.

.. code-block:: python

    class Alot(Correct):
        auth = (OAUTH_TOKEN,
                OAUTH_SECRET,
                CONSUMER_KEY,
                CONSUMER_SECRET)
        phrases = [...]
        cooldown = (...)
        dry = True

        def reply(...):
            # ...