Community
Participate
Working Groups
I would be nice to easily enable flux server from the IDE. I imagine a "Flux Server" Run configuration that would simply let user configure ports and start Flux (and maybe even Orion) to easily share parts of workspace with others. JSDT now includes some Node.js (and npm?) support in master. Those could be leveraged to easily start Flux.
Agree, sounds indeed like an extremely useful feature. Since there is no active development for Flux at the moment, I don't expect much activity from the project committers at the moment, but contributions would be more than welcome. It looks to me like the project is morphing itself into a proof-of-concept-like project instead of a production-ready open-source product that you can (re)use.
I think flux doesn't need to be "production-ready" or robust to be use in our real life. I see a flux session something that will just run for a while and that you throw away when you finish the session. Participants number would be from 2 to 10. I really see the usage of flux like this. In the eclipse platform, we could start flux with docker or the embedded nodejs and automatically share this with ngrok. Once we finish, just stop it. In Eclipse Che 3.x, this is how I wanted to do by running it inside a docker container. I'm starting to adapt the plugin to Che 4.0 in this way.
I agree with Sun. To me, Flux is not something that stays always running on a Cloud server, it's more something to use for small network for a specific activity, more in a peer-to-peer mode. One developer would start a coding session, and invite some others to join (with whatever editor they want). When they're all happy of the status of that work, the code is committed, all developers thank one and other and the session is stopped. Flux is not a terminal application for development, it's a tool for existing development terminals such as Eclipse IDE or Che. Considering how to get incorporated as best into those tools is IMO the key factor of success.
I agree and like your proposal very much. Just wanted to mention that we don't have people actively working on this at the moment. Therefore the call for contributions... :-)
This feature should be run on cloudfoundry right? I don't see the point of run it locally...
(In reply to Xin Wei from comment #5) > This feature should be run on cloudfoundry right? I don't see the point of > run it locally... Don't you remember the time of local LANs game playing Counter-Strike or age of Empires? On a local network, the one with the bigger machine says "let's start a team coding session, I started one at [IP address]" and others just join on demand. But indeed, this scenario is only for local networks, for the WWW, a Flux Server on the cloud is better.
The idea behind this feature is clearly to startup something quickly from the local machine, without the need to host anything remotely on a cloud environment.
New version of JSDT includes Run Configuration for nodejs and npm. It's probably something that can be reused to create a "Flux Server" Run Configuration from the IDE.
