Skip to content

Universal Tooling/Aliases and Hierarchy #28

Description

@AaronFeledy

Devtool could provide a cross-platform alias/tooling management platform to meet the needs of not only a single project, but an org, a specific host, or an individual developer.

  • Project-based tooling, as always
  • Host-based tooling that can be run anywhere on the machine, based on Host commands based on Bun $Shell #20, basically sharable, pluggable aliases
  • Org-defined tooling that applies to any of the org's projects/apps. Maybe this is just a plugin required by each of their projects
  • User-defined tooling (.devtool.local.yml)
  • Establish a hierarchy for overriding tooling so that a general org-based command can exist that can be overridden by a more tightly-scoped definition like host, app, local, or user.
  • Maybe there should be separate local and user scopes so you can have config for a local environment, similar to a .env file used only on prod, then a user scope for a dev's personal preferences that overrides everything else.
  • Maybe implement a concept similar CSS's !important to prevent overriding

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions