Navigation Menu

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.

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

Binary executable deploy? #4

Closed
halybang opened this issue Sep 5, 2017 · 4 comments
Closed

Binary executable deploy? #4

halybang opened this issue Sep 5, 2017 · 4 comments

Comments

@halybang
Copy link

halybang commented Sep 5, 2017

We can not deploy hexya as binary executable when invoke hexya server (because of calling cleanModuleSymlinks/createModuleSymlinks ).
IMHO, cleanModuleSymlinks/createModuleSymlinks should be call when invoke hexya generate

@npiganeau
Copy link
Member

Hexya cannot be deployed as binary anyway:

  1. Because it needs all resource files (from all the folders which are symlinked) as you said
  2. Because it is configurable at compile time (to choose the modules you want).

So because of 1 and 2, I did not put much importance about deployment for the moment.

But I plan to do a hexya bundle or equivalent to get a distributable form of Hexya (maybe a zip or a single binary with go-binddata, I don't know yet)

@halybang
Copy link
Author

halybang commented Sep 6, 2017

I created a simple application for do that. Still need to move cleanModuleSymlinks/createModuleSymlinks to another location.
You can look :)
Haxey

@npiganeau
Copy link
Member

Ok. Can you make a PR ?

@npiganeau
Copy link
Member

Done in 9f2d33f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants