Skip to main content

Service development environment manager

Create and mange an environment for services you need to develop complex (web/network) applicaitons.

Each service runs as docker container that is managed by a compose file.

Usage

just copy the run.bash-file in your projects root directory and run it. (We will have a wizard in the future to cretae new services)

It will ask to install docker and docker compose if they are not installed.

At first run it asks to install as local virutal environment inside your project and adds this to your .gitignore.

To show external windows with logs and run a bash inside your container it uses tilix. You can also select other terminals (like terminator) but only tilix supports all features, so its recommended to use with tilix.

Features

  • just one run.bash-script needed to manage the whole project.
  • keyboard-shortcuts and args to start, (re)build, show logs and deploy services.
  • exposes user id, user name and group id to docker environment allows you to run services as local user.
  • include provided env-file for secrets and deployment.
  • runs external terminal windows (tilix) for logs with automatic tiling of the windows.
  • service status (written in file, either watched by inotfiy or pulled from file system)

Screenshot

Metadata

Release files for service-dev-env 0.7.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for service-dev-env 0.7.3
File Interpreter ABI Platform Actions
service_dev_env-0.7.3-py3-none-any.whl Python 3 none any Details for service_dev_env-0.7.3-py3-none-any.whl

Release files / service_dev_env-0.7.3-py3-none-any.whl

Download URL service_dev_env-0.7.3-py3-none-any.whl
Size 26.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
703ee89854b393afda00f7814217796720a7b570c17f0b1dbf401edd4ece8208
BLAKE2b-256 checksum
How to use checksums
9ff13142ddb508e50bb200c61e6f2fc9a0e0570822910b98050886d7ea9f3c5e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Security for service-dev-env 0.7.3

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page