Skip to content

Guide on deployments harder #63

@dawsontoth

Description

@dawsontoth

The general gist is that we can add a tool for deployments.

  1. When invoked, this tool will see if you're configured for deployments.
  2. If not, we can pop open a nice UI to guide them through registration and providing the right details.
  3. We'll save those into their .env file.
  4. Then the tool can do the deployment (by invoking the npm deploy script)
  5. We can guide them on setting up the right workflows and secrets (eventually).
  6. Also provide a few more tools:
    a. Check configuration (can we actually access the API?)
    b. List current deployments
    c. Return URLs for the deployments so they can pop it open in a browser.
    d. Read logs to see if the deployment succeeded.

This was instigated by a conversation with the agent that showed it didn't really know:

User: how do i deploy this app to fabric?

Agent: To deploy the app to Fabric, we'll need to set up the deployment configuration. Microsoft Fabric is a unified analytics platform that can host web applications. Let me guide you through the process of deploying your HarperDB application to Fabric.

🤦

Metadata

Metadata

Assignees

Type

No type
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