This release is a pre-release and may not be stable for production use.
[](https://waffle.io/code4maine/beehve) Beehve ======
[](https://travis-ci.org/Code4Maine/beehve)
Inspired and heavily copied from [laddr](http://github.com/CfABrigadePhiladelphia/laddr), Beehve aims to be a one-stop-shop for what’s going in our Code for America Bridage in Maine: Code 4 Maine. Mostly, as a Django dev in my other life, I couldn’t stomach hacking on the PHP codebase of laddr. So hopefully we can get this app to a place where it will meet our needs and be highly extensible as well.
Of course there are always trade-offs, and, as a Django app, deployment is not what it could be. But hopefully I can get it hooked up with Herkou and make it pretty easy to get started.
Features include:
Project tracking
Members directory
Github integration
Project buzz
Big screen for public events
Not all of these work yet, but we’re on way to a 1.0.
Deployment
Deployment of Beehve is done via the ansible roles found in the ansible directory (tada …). Usage of these roles is contingent on a few configuration details:
Configure your target hosts in the ansible/hosts file
Copy ansible/hosts_vars/www.example.com ansible/host_vars/www.yourdomain.com
Fill in the details of the host_vars file
Run: `ansible-playbook -i ansible/hosts --limit production ansible/all.yml`
Easy bootstrapping!
Powered by the ubiquitous Makefile … this should be pretty easy:
make install
make run
open your browser to: http://127.0.0.1:45000
Alternately, you can build a vagrant box, in case you’re not on Linux:
vagrant up
That’s pretty slick, but will also come with some “issues”
Librarys, librarys, librarys!
Of course, we could provide a vagrant file and a provisoner and all that jazz. But I’d rather provide a make file for installing everything into a venv and let you muck about with libraries. Those of you on Linux shouldn’t have too much trouble installing the requisite development libraries below. The names are for debian-based distros, but they exist for all major distros.
On Mac it may be a little tricker. Homebrew will get you quite far, but first you have to install the bloated XCode and the CLI tools.
The libraries are:
libmemcached-dev
libfreetype6-dev
libjpeg-dev
Metadata
Release files for beehve 3.0.0.dev5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| beehve-3.0.0.dev5.tar.gz | 9.4 MB | Without provenance | Details for beehve-3.0.0.dev5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| beehve-3.0.0.dev5-py3-none-any.whl | Python 3 | none | any | Details for beehve-3.0.0.dev5-py3-none-any.whl |
Total release size: 18.9 MB
Release files / beehve-3.0.0.dev5.tar.gz
| Download URL | beehve-3.0.0.dev5.tar.gz |
|---|---|
| Size | 9.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2cc253e7bf702cc344ff800fc51e76812c11dd8fd39f732e4a1a05666914f34
|
|
BLAKE2b-256 checksum How to use checksums |
e188fc8f6ebe3cfd993028670dbe0ab5b5630f369ddf83f6159804c8a40a4b96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / beehve-3.0.0.dev5-py3-none-any.whl
| Download URL | beehve-3.0.0.dev5-py3-none-any.whl |
|---|---|
| Size | 9.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b023b37026d5d876daf4b927eec678c3d3bb6d5f04203e64ca23efc93396e2c
|
|
BLAKE2b-256 checksum How to use checksums |
c51b0af447d6c51409991c12c99583f4fe758fd50289088a72432567824ae351
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for beehve 3.0.0.dev5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.