-
Notifications
You must be signed in to change notification settings - Fork 19
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
Docker 3 #385
base: main
Are you sure you want to change the base?
Docker 3 #385
Conversation
} | ||
}); | ||
} else { | ||
error!("Failed to upgrade global context, cannot clean up docker container session"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"shotdown detected, just quit"
|
||
RUN cargo build | ||
|
||
RUN mkdir -p /output && cp target/debug/refact-lsp /output/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm why /output ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Dockerfile is primarily for building refact-lsp for development. We’ll extract the binary to the local machine. The /output directory is a bit generic, but I've seen it a few times; if you have a clearer name suggestion, we can rename it.
38f9036
to
9041fef
Compare
16cd255
to
9552cf2
Compare
…ntainer and expose to all interfaces only from container
…port yet, note the frontend is still calling it
…d whenever is necessary
…, and to sync to container
No description provided.