-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Console layer #141
Comments
is this what you are looking for? #84 |
No, is more like this console app in buchu |
we could have something like does it make sense? |
But about the transport/execution layer? Will be a console app or HTTP? |
I agree with the @jhomarolo My suggestion is to create a simple folder inside the infrastructure layer so inside it we could have an index.js for me it could be an |
there is no transport layer. the |
@dalssoft since there is no transport layer, how the project will run inside a cronjob or scheduled task? |
for a cronjob would be ok to just it on a remote terminal as CLI (#141 (comment)). for scheduled task, like a lambda, this is just a rest or graphql endpoint waiting to be called by a lambda, already supported. |
#141 (comment) looks interesting but it is the same as herbs2repl, no? |
Is your feature request related to a problem? Please describe.
What do you think about the CLI creating a console layer?
Describe the solution you'd like
Instead of using the HTTP layer (rest or graphql), maybe the cli could create a console layer, for background processes or cronjobs.
Describe alternatives you've considered
Create a cronjob layer directly
The text was updated successfully, but these errors were encountered: