feat: move use cases to connections #36
Conversation
✅ Deploy Preview for hoopdev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
krol3
force-pushed
the
move-usecase-to-connections
branch
2 times, most recently
from
7ce7b10
to
275c229
Compare
|
run |
krol3
force-pushed
the
move-usecase-to-connections
branch
from
275c229
to
106df01
Compare
|
@andriosrobert could you check the preview? |
|
I like it, but I still see the use cases folder with one item. I would remove this menu and keep everything inside connections other than that, I like this a lot! |
I left this use case "scripts", for me, it could be our first use case, it contains video and explains a complete flow. https://hoop.dev/docs/usecases/scripts @andriosrobert |
I left this in the use case, because for me, it could be our first use case, it contains video and explain a complete flow. https://hoop.dev/docs/usecases/scripts |
Signed-off-by: carolina valencia <krol3@users.noreply.github.com>
Signed-off-by: carolina valencia <krol3@users.noreply.github.com>
krol3
force-pushed
the
move-usecase-to-connections
branch
from
b4b1b6d
to
a979e53
Compare
docs/connections/heroku-oneoff.mdx
Outdated
| --- | ||
|
|
||
| import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton'; | ||
|
|
||
| # Heroku one-off | ||
| # Heroku execute task one-off |
There was a problem hiding this comment.
maybe I would change the task to session here. I say that because task is a Runops concept and I would want to avoid confusion but maybe it's here for a reason that I don't know
There was a problem hiding this comment.
This is related to heroku one off dynos:
https://devcenter.heroku.com/articles/one-off-dynos
docs/connections/ecs-exec.md
Outdated
|
|
||
| The Elastic Container Service allows executing one off tasks of any type directly into ECS tasks/containers. | ||
| Interact with Elastic Container Service executing one off tasks or an interactive session into ECS tasks/containers. |
| --- | ||
|
|
||
| import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton'; | ||
|
|
||
| # Heroku | exec | ||
| # Heroku | interactive |
There was a problem hiding this comment.
I believe interactive is the command "connect" not the "exec". I always make misunderstand these kinds of commands, hahaha, but I believe that "exec" is not interactive.
What do you think?
There was a problem hiding this comment.
The psexec allows connecting both interactive and non-interactive as do heroku one-off. The difference between then is that ps-exec executes stuff inside a running dyno and the other one executes in an one off dyno:
https://devcenter.heroku.com/articles/one-off-dynos
docs/connections/ecs-exec.md
Outdated
| hoop connect my-ecs -- --pipe clojure | ||
| ``` | ||
|
|
||
| ## AWS ECS - Execute one task off |
There was a problem hiding this comment.
task to session here as well
There was a problem hiding this comment.
I think it's better to call "One Off Execution" @mtmr0x . The session is derived from an execution.
|
Also, we already have "Postgres" native and I believe we have "MySQL" as well, but I would ask Sandro before implementing it. |
I believe this one is lost in this connection session. Is this from "user guides"? |
It's already documented: https://deploy-preview-36--hoopdev.netlify.app/docs/connections/mysql |
Signed-off-by: carolina valencia <krol3@users.noreply.github.com>
krol3
force-pushed
the
move-usecase-to-connections
branch
from
0d8d66c
to
3c8b5f4
Compare
|
lgtm |
move use cases to connections