-
-
Notifications
You must be signed in to change notification settings - Fork 353
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
Running a standalone binary from package sources only in docker multistage build #311
Comments
Hi there, just giving some news about this issue. I had been working for a while on the next version of this package and I'm currently finishing up things for a near to come release. While there will be breaking changes, a Docker example that shows how to run an app created with this package will be added to the You can take a peek here. |
Great stuff, I had a chance to briefly go through the changes. I can see that the direction the app is heading to is more or less a full-blown framework with its own bindings for all html interfaces and js events. That is quite a departure from the previous versions where it was a mere wrapper of raw markup. Would it still support raw markup as well as bindings or the focus will be towards enclosing the ecosystem in its own objects ? |
The focus will be on its own objects. There will still be a raw element: raw := app.Raw(`<h1>Hello world</h1>`) It takes raw HTML string argument but it will be limited compared to the current version (no event handler). |
Hi there, here is a docker example on how to use the package with docker: Gonna close this issue. |
Hello and thanks for creating this very neat framework.
I am trying to build a minimal multistage docker build running from binary without the goapp CLI.
I have seen that a binary for mac was accomplished in older threads. Is that doable on Linux as well ?
I am not sure what's the exact flow behind
goapp run -v -b default
but looking at the code it's running the server only.Example Dockerfile:
Example output:
ReferenceError: Go is not defined error
Based on this similar topic it seems that the issue is somewhere in
The text was updated successfully, but these errors were encountered: