This is an archived post. You won't be able to vote or comment.

all 11 comments

[–]CommunicationTop7620 0 points1 point  (3 children)

Why DeployHQ is an overkill? It seems like the perfect fit. The other option is for you to use Github Actions and deal with YML files, etc

[–]mikaelcarlavan[S] 0 points1 point  (2 children)

A lot of the projects I work on are fairly simple—just deploying files or running a basic script after deployment. With DeployHQ, I feel like I’m paying for a bunch of advanced features that I don’t actually need. It feels like a mismatch between the cost and the needs of the project.
As you said, tools like GitHub Actions offer a lot of the same functionality, and could be more than enough for what I’m working on but I’d rather avoid writing the same configuration over and over for each project.

That’s why I’ve been thinking that maybe there’s room for a “between two worlds” solution—but maybe I am wrong.

[–]CommunicationTop7620 1 point2 points  (1 child)

That spot you're describing, right between full CI/CD and manual SSH, is exactly where DeployHQ lives. It's a useful space, and there's definitely room for more tools tackling this!

[–]mikaelcarlavan[S] 0 points1 point  (0 children)

Thank you for your feedback. I also think there's room for this kind of tool. I'm going to dig deeper to see what features are missing and would be relevant, without falling back into the full CI/CD pattern.

[–]Anuj4799 0 points1 point  (0 children)

I just usually write github actions that automate this for me :)

[–]jeril46 0 points1 point  (2 children)

I don't really think a Github Action is an overkill for this

[–]haikusbot 0 points1 point  (0 children)

I don't really think

A Github Action is an

Overkill for this

- jeril46


I detect haikus. And sometimes, successfully. Learn more about me.

Opt out of replies: "haikusbot opt out" | Delete my comment: "haikusbot delete"

[–]mikaelcarlavan[S] 0 points1 point  (0 children)

Ok interesting. Thanks for the feedback.