Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Re-inventing Herokuish? #18

Open
asmr-hex opened this issue Apr 2, 2018 · 1 comment
Open

Re-inventing Herokuish? #18

asmr-hex opened this issue Apr 2, 2018 · 1 comment
Assignees
@asmr-hex @frenata @nefelin
Labels
question Further information is requested

Comments

@asmr-hex
Copy link
Collaborator

asmr-hex commented Apr 2, 2018

I recently stumbled across this repo called Herokuish and it seemed p relevant to what we are trying to implement here though definitely larger in scope. I just want to call this out s.t. we aren't re-inventing the wheel.

Because xaqt is specifically focused on running ephemeral processes in a safe way (not running long-standing processes (as i am guessing Herokuish is aiming to support), I think we are fine, but just wanted to point this out.
@asmr-hex asmr-hex added the question Further information is requested label Apr 2, 2018
@frenata
Copy link
Owner

frenata commented Apr 5, 2018

That's interesting...

Somehow simultaneously much larger and much small in scope.

I know part of your plans were originally more oriented towards longer running processes, but I guess in some sense they are still ephemeral.

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

@asmr-hex asmr-hex

@frenata frenata

@nefelin nefelin

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@asmr-hex @frenata @nefelin