Skip to content

A web UI #78

Description

@mehulkar

One of my concerns is separating the task of deploying and developing. This breaks down into a couple things:

  1. Making new builds available
  2. Deploying new builds.

I'd like our deploy process to look like this:

  1. Update source control (either tag a new release, or push new code, whatever)
  2. Deploy team is notified of new build available (or polls for new builds)
    • This is unimportant, but Github webhook, or cron job on deploy servers are both trivial to implement)
  3. Deploy team opens up web UI, sees available builds and clicks a button for the build they want to deploy (for whatever target, e.g. staging, prod, etc).

I can see this web UI as an addon/plugin based on @lukemelia's talk at EmberConf2015, but wanted to get thoughts on the use case.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions