http://www.elitedangerouscentral.com (route planner, trading tools, system browser and more -always adding features-)
11 Jan 2015
First of all, if you experienced some service interruption during the last two days I want to apologize, as I was running tests and had to be done on the live server.
After much exploration, playing 'sysadmin', testing and fighting with different technology stacks, server side, client side, writing code and what else; I've found a more or less permanent solution to some of the problems (and potential problems) of running an intensive app on limited resources without much control over the server (using a Openshift PaaS for the curious techies)
While I can do some minor polishing regarding the automatic deployment in case of failure or server restart (there may be temporal outages of some services if this happens, but shouldn't, at least too often), I'm comfortable enough with the current set up. And apparently it has been running for a day w/o much problem.
From now on I will be making some of the features 'asynchronous', what this means for you is no frustrating time outs, in fact works would survive even a computer crash on the client side (but you won't be able to retrieve them, not with some additional coding on my part and some session cookies voodoo, which I don't find worth the effort right now). This also means the app will be able to scale easily (I plan to support it with my local machine after some investigation hopefully) in case I changed hosting and could process thousands of tasks in parallel plus some other 'cool stuff'.
Hopefully this will free me in the future of having to fight hardware or hosting service limitations(at least somehow), give you a better service, and free me to do add features without having to worry about some things (unfortunately, not all, as the db may end up being overrun time to time). For now just the current trade calculator is asynchronous, but the route planner will follow soon. As well as some other potential tools in the future which would require some processing time etc. If you experience problems let me know as I'm uncertain yet how well this will work (but for now seems to be doing ok). Cheers!
11 Jan 2015
First of all, if you experienced some service interruption during the last two days I want to apologize, as I was running tests and had to be done on the live server.
After much exploration, playing 'sysadmin', testing and fighting with different technology stacks, server side, client side, writing code and what else; I've found a more or less permanent solution to some of the problems (and potential problems) of running an intensive app on limited resources without much control over the server (using a Openshift PaaS for the curious techies)
While I can do some minor polishing regarding the automatic deployment in case of failure or server restart (there may be temporal outages of some services if this happens, but shouldn't, at least too often), I'm comfortable enough with the current set up. And apparently it has been running for a day w/o much problem.
From now on I will be making some of the features 'asynchronous', what this means for you is no frustrating time outs, in fact works would survive even a computer crash on the client side (but you won't be able to retrieve them, not with some additional coding on my part and some session cookies voodoo, which I don't find worth the effort right now). This also means the app will be able to scale easily (I plan to support it with my local machine after some investigation hopefully) in case I changed hosting and could process thousands of tasks in parallel plus some other 'cool stuff'.
Hopefully this will free me in the future of having to fight hardware or hosting service limitations(at least somehow), give you a better service, and free me to do add features without having to worry about some things (unfortunately, not all, as the db may end up being overrun time to time). For now just the current trade calculator is asynchronous, but the route planner will follow soon. As well as some other potential tools in the future which would require some processing time etc. If you experience problems let me know as I'm uncertain yet how well this will work (but for now seems to be doing ok). Cheers!
Last edited: