No no no! There is no sharing of credentials. Essentially you create an app with the required scopes. Use those scopes to make an oath token request link (to CCP's domain). Once authenticated the user authorizes the token request and is redirected back to your application's callback URL. The information provided at to your callback includes a token and refresh token. You will use the refresh token to obtain a new token whenever the primary token expires.
That's a very rough description of the process. Digital Ocean has a decent diagram to describe the oauth2 process: https://www.digitalocean.com/community/tutorials/an-introduction-to-oauth-2
More info on how to make requests with your token to the endpoints: http://eveonline-third-party-documentation.readthedocs.io/en/latest/crest/authentication.html#using-your-access-token
To practice and learn how to install software on a Linux box I can recommend setting up a virtual machine on your PC with Ubuntu server and just give it a go. If something goes wrong you can just spin up a new virtual machine.
e.g. https://www.virtualbox.org/ is a great SW to create VMs and its free.
So is Ubuntu server
Damn, looks like there aren't any ARM packages for PHP5.6. (Running on an older Cubietruck).
Right. Sorry about that, wasn't sure how to upload the code properly. Here it is: http://codepad.org/1Xi6osL8. As for timers, I have it set to 5 minutes and then conduct a re-check, is that too frequent?
I don't have anything broken out, I'm afraid.
Not hellishly difficult to do though. (I don't want to maintain yet another file, which is why I'm saying how)
Grab the latest sqlite version https://www.fuzzwork.co.uk/dump/sqlite-latest.sqlite.bz2
unzip it (7zip will do nicely)
open it up in a tool which allows for queries and exporting. The command line tool does it. as does http://www.speqmath.com/tutorials/sqlite_export/ (I've yet to come across an sqlite browser which does)
select it.typeid,typename,it.typeid from invTypes it join invGroups ig on it.groupid=ig.groupid where categoryid=7 and it.published=1 order by it.typeid asc
is the sql you'll need to pull just modules (which includes rigs)
I haven't tried it and I don't do PHP at all so I'm not going to, but I don't see why it wouldn't work.
You would need to write your own adaptor for Eve SSO (no ESI) as described in the documentation.
If you aren't so sure about your experience messing about with boxes, I would suggest installing virtualbox, then install whatever unix flavour you want (centos 7, or ubuntu or whatever).
This way you can mess about, take snapshots (backups), and get used to how to install SeAT etc...
Once you are happy and know what you are doing more, then start paying for a VPS from somewhere.
Google has a request limit for UrlFetchApp. According to the Services Dashboard (https://script.google.com/dashboard) it's 20k per day, and every cell counts as a call, every time it refreshes, and even if there was an error. Basically, if you're trying to make 900 calls, it could be that you're hitting that limit quick.
>I've added in a delay to the script
How exactly did you do this, because if you didn't use a CacheService or LockService call, then the scripts may not know about eachother and you may still be bombarding CREST with 900 simultaneous calls and you're limited to 20. You can make 150 calls per second, or 400 burst.
JSON numbers are not limited in size, so the strings are technically redundant (http://json.org/number.gif). A pragmatic approach to reduce the redundancy and work around javascript limits would be to use strings for ids (which may need 64 bits, but don't need to support arithmetic) and JSON numbers for everything else (I doubt even PL have more than 9007199254740992 ISK so a 64 bit float should be fine).
First off, I recommend considering a different tool that is being actively maintained if there isn't something specific to EWS that you need.
I'm not entirely sure that Dockerfile ever actually worked. It was contributed and I didn't test it before merging the PR. Even if it did work, it should only be used for testing since the resulting container has way too much going on for a thin container (DB, RabbitMQ, Nginx, EWS Application, and EWS workers running in the same container).
If you still want to try it out, I'd suggest installing it in a VM or a fat container (i.e. LXC) with an init system using the instructions here.
Could you include my EVE Mining Timer app (Android only for now)?
https://play.google.com/store/apps/details?id=com.digital_tectonics.eveminingtimer
I can't point to PHP libraries and what not, but here're some general words.
I'd start to learn with Python. It's newbie friendly, has a vast amount of libraries, and it scales with what you want to do. Back end servers, web sites, desktop apps. Even Eve. Although it's not the fastest language it's certainly one of the easiest languages to get into.
Depending on who you ask, you'll be told coding is either a hobby, a craft, an art, a science or just a job. I think it boils to attention to detail and avoiding procrastination. To help get into that mindset, I tend to recommend this: https://www.amazon.co.uk/Pragmatic-Programmer-Andrew-Hunt/dp/020161622X
Once you get onto the path, you'll be buying lots of books. Worse, hording them.
Once you've got the basics - got a couple of apps running successfully - I'd suggest you get a firmer, more "computer sciencey" bedding: if you're like me, "complex" is often a good thing. CS will help you make complex things run faster and in less development time.
And MIT just happen to use python and they publish some old lectures: https://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-0001-introduction-to-computer-science-and-programming-in-python-fall-2016/ If maths is not your strength here's a really simple rule: just keep an eye on ratios, such as "how much work can I achieve in 1 step?" and you'll have beaten many developers.
And that rolls into the final point: be sure you want to do this. Many have tried, and normally chilled people will rage in frustration. Like Eve, software needs commitment & time.
The very best of luck in your travels.