3 ms·
That post seems to talk about how to implement this functionality yourself - as in, what the server should do when someone pushes new changes to it. In the cas
by crb 13y ago
That post seems to talk about how to implement this functionality yourself - as in, what the server should do when someone pushes new changes to it.
In the case of App Engine, Heroku, Azure etc, that is all abstracted away from you - as is, in many cases, the concepts of binaries. You just package up and upload some code somehow, and their "mesh" decides where to deploy it and how to run it.
(I know Heroku gives you a little more control over this; with App Engine, you get a config file and a number of instances you can tweak, and that's about it in the general case.)
This is so far available for Python and PHP - not Java or Go.
- ImJasonH 13y agoExactly. While the article makes very good points about what you want from a general-purpose Git deployment script, deploying to App Engine is not quite the same, since there is no Git client on the server pulling changes directly, so you avoid the problems addressed by all four points. App Engine creates new app instances when you deploy, so there's no need to care about deleted files, tracked/untracked files on the server, and so on.