Fling
Fling is a side project management platform.
Fling is a tool for those of us who cannot help but create new side projects - flings. Some flings are started late at night and forgotten about the next day, while others we may continue working on over many weekends. Some may generate income, while others drain our savings. With so many projects in some state of development, keeping track of your flings, your fling's social media accounts, user activity or even where they're hosted can be nothing short of a nightmare. This tool is meant to help with that.
Fling allows you to collect and store "business state" separate from both the source code (which lives in a git repo), and app state (which usually lives in a production database somewhere).
Business state is:
- Hosting details (where is it running)
- Socials (blog, insta, mastodon)
- Monthly costs
- Income (revenue or donations)
- Basic user stats (views, signups, sessions)
- Partnership details (who built it with you)
- History / Timeline (when was it started, deployed etc)
It consists of a CLI tool, a web service, and a cookiecutter template.
The CLI, along with a growing set of plugins, can be used to gather "business state" about your project, and store that in the Fling service.
The cookiecutter template is language agnostic, and can be used for any new side project. It will add a company-private web interface that can be used to browse and visualize your side project state.
The Fling web service can be authenticated with GitHub, and used to aggregate the Fling business state from all of your side projects.
Fling CLI plugins
Namer
The namer plugin can be used through the search command. It uses ChatGPT to
come up with great domain name ideas, and then the Name.com API to find some that
are available.
Init
The init plugin is integrated with cookiecutter, and can be used to set up a new
side project with Fling support. Existing projects can be configured by manually
creating a fling.yaml file and then running fling pull.
Metadata
Release files for fling-cli 0.1.7
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 |
|---|---|---|---|---|
| fling_cli-0.1.7.tar.gz | 6.5 kB | Without provenance | Details for fling_cli-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fling_cli-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for fling_cli-0.1.7-py3-none-any.whl |
Total release size: 14.4 kB
Release files / fling_cli-0.1.7.tar.gz
| Download URL | fling_cli-0.1.7.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59e94f0b0cbb7eb9f20eac972c4572dbc60afc542fc1bb8de8b1e3b717977140
|
|
BLAKE2b-256 checksum How to use checksums |
8556127c8a3e9ba0e6f08de7f566a33f669f4970fde55a3dd9f18c3fa2644de1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.9.6 Darwin/22.5.0
|
Release files / fling_cli-0.1.7-py3-none-any.whl
| Download URL | fling_cli-0.1.7-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
779df528807189d01d8bc30d051242e7b9995dfc7b6da11680c4207ed4d54d79
|
|
BLAKE2b-256 checksum How to use checksums |
5c2d34e769f0f21234f5f35ace88e6c9346c86a38a3266484d2abe929bd1ffd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.9.6 Darwin/22.5.0
|
Security for fling-cli 0.1.7
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.