Spire
Bugout custom knowledge bases
Setup:
- Clone git repository
- Install postgresql (https://www.postgresql.org/download/linux/ubuntu/)
- Install elasticsearch (https://www.elastic.co/guide/en/elasticsearch/reference/7.9/deb.html)
- Install requirements
- Create dev version and manage app at https://api.slack.com/apps/
- Copy sample.env to dev.env and fill
devfields
export BUGOUT_SLACK_[your info for slack apps]
...
export SPIRE_DB_URI="postgresql://postgres:postgres@localhost/brood_dev"
export ELASTICSEARCH_[your info for elasticsearch]
...
export BUGOUT_JOURNAL_EMOJI="beetle"
export SPIRE_API_URL="http://0.0.0.0:7475"
export BUGOUT_AUTH_URL="http://localhost:7474"
- Copy
alembic.sample.initoalembic.dev.iniand correct field
sqlalchemy.url = postgresql://postgres:postgres@localhost/brood_dev
- Run alembic migration
> ./alembic.sh -c alembic.dev.ini upgrade head
- Install ngrok (https://ngrok.com/download)
- Run ngrok tunnel
> ngrok http 7475
- Run server
> ./dev.sh
- Set slack
OAuth & PermissionsRedirect URLs to ngrok
https://60843a634907.ngrok.io/slack/oauth
- Add OAuth Scopes
app_mentions:read
channels:history
channels:read
chat:write
commands
emoji:read
groups:history
groups:read
im:history
im:write
links:read
mpim:history
reactions:read
reactions:write
users.profile:read
- Set slack
Event SubscriptionsRequest URL to ngrok
https://60843a634907.ngrok.io/slack/event
- Add events
app_mentions
app_uninstalled
channel_rename
emoji_changed
link_shared
message.im
reaction_added
reaction_removed
- Run brood local server
- Create brood user
slack_installationwith hard password (this user will be managing whole slack workspaces), generate token for this user and add it to environment atdev.env
export BUGOUT_INSTALLATION_TOKEN="<installation user token from brood>"
-
Add slack dev bot to slack
-
For Shortcuts use readme (https://github.com/simiotics/spire/blob/bug-9-visual-slack-search/spire/slack/shortcuts.md)
Metadata
Release files for bugout-spire 0.4.2
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 |
|---|---|---|---|---|
| bugout-spire-0.4.2.tar.gz | 110.2 kB | Without provenance | Details for bugout-spire-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bugout_spire-0.4.2-py3-none-any.whl | Python 3 | none | any | Details for bugout_spire-0.4.2-py3-none-any.whl |
Total release size: 250.0 kB
Release files / bugout-spire-0.4.2.tar.gz
| Download URL | bugout-spire-0.4.2.tar.gz |
|---|---|
| Size | 110.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
916e41f395fd839d2b02cf346997b56adf29da15a66c2cd14e2f79ba896a79d4
|
|
BLAKE2b-256 checksum How to use checksums |
df2fbda30451e1e97569d400db9bd4618958cb32eb4ab8f87b264e0ce39d6d62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.13
|
Release files / bugout_spire-0.4.2-py3-none-any.whl
| Download URL | bugout_spire-0.4.2-py3-none-any.whl |
|---|---|
| Size | 139.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
054cabaa80d2f7be2e78a9f5295c72a2ecbd156bc929559d7fe76eaf5b2654ba
|
|
BLAKE2b-256 checksum How to use checksums |
c17d1904a64df2f1c47adb96f12a61b7dce9e4337530e81512473bcecfddc54e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.13
|
Security for bugout-spire 0.4.2
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.