-
Notifications
You must be signed in to change notification settings - Fork 250
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
Dynamically linked libraries with docker support #1190
base: develop
Are you sure you want to change the base?
Dynamically linked libraries with docker support #1190
Conversation
Added compilation of dynamically linked libraries
db entity fix added sql. NullTime struct
94ae0c5
to
01e7379
Compare
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.
This is an awful lot of code and, aside from the functions in src/core
, I'm not sure that any of it needs to be in the mainline Yggdrasil distribution. Especially database code, for which it's not clear to me what its purpose is.
As I see it, it's currently impossible to save information from the API such as Peer info, etc.(Now it’s only possible to monitor). Moreover, after the session ends, this information is not available in yggdrasilctl, so the database is used to store the data. Dynamic library compilation can be useful if you want to use Yggdrasil in .NET (for example in your ASP NET project you just need to create a custom marshaler). In my opinion Cobra command fits better than Flags. |
Added dynamic library generation, so now it's possible to compile the library and use it in your .NET project.
Flags have been replaced with Cobra commands (Docker launch has been maintained).
Added a database to store all data retrieved from the API.