-
Notifications
You must be signed in to change notification settings - Fork 306
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
Project status #114
Comments
Hi, thank you for your interest in Flux. a) Project is currently under active development with a minor release of 65.
b) Currently to development focus of the project is being pushed towards launch of global applications.
Firstly I shall talk about how even apps (which essentially is a docker) are spawned on flux and why we need some further scanning of zel chain. Spawning an application works in 3 steps.
Then there is the other stuff regarding application management post launch, such as modifying, updating, executing commands, extending and so on. That needs to be completed before public launch as well but is less time consuming Project is actively developed in develpoment channel, master channel is for stable releases from which Flux nodes get their code. You can also check out portion of Flux documentation at https://github.com/zelcash/zelfluxdocs https://zelcash.github.io/zelfluxdocs/ or if you prefer swagger ui at https://zelcash.github.io/zelfluxdocs/swagger-ui/ c) I think this touches style of coding. It surely can be improved and someone may prefer many small files, splitting it. I have set it up this way where one file touches one portion of flux. Eg. zelappsService touches all services of the applications which consist of services, some helping functions, some api functions. That all can be splitted. Most likely several functions will be rewritten later to better support test suite. d) Such a document is not really in existence. Several specifications are documented in the code where living as live schemes before actually coding it or in zelflux docs. But since basically all work is done by me, I never really bothered to write publicly write some more robust specifications - eg. specifications messages between flux, zelapp registration specifications, signing of api calls, sequence of apps creation/ registration. Most of it can be deducted from the code and a sample UI included. But I agree that such a document is crucial for ongoing development and community participation |
All three points described are now finalised, tested (even live publicly) and will be in production soon. |
Flux v1.0.0 is now released and users can begin spawning their own applications very soon -> release notes :) |
Some questions for the developer:
What is status of this project?
Where is development happening?
Why are some existing source code files hundreds of lines long?
Where can one find the specifications this software is being built from?
The text was updated successfully, but these errors were encountered: