Hello George, Thank you very much for your explanation. What I'm trying to establish is, why the developing company wrote the site in Python using GCE instead of using GAE when per our contract, they should have used GAE from the start. They stored the files in an external repository and deployed it in my GCE account. Now, they say they fulfilled the contract but I don't agree.
On Friday, December 1, 2017 at 6:36:22 PM UTC+1, George (Cloud Platform Support) wrote: > > Hello Torsten, > > You are right, you cannot just move a project to GAE, but you can use your > existing GCE programming code for the app, open a GAE project and deploy > the code in accordance with GAE guidelines. The "Deploying the Application" > documentation page [1] provides more detailed information on how to deploy > to the GAE. > > Your code might need some adapting and re-writing prior to such GAE > deployment, mainly if your code had made use of local storage when running > the app on the GCE. In App Engine, the local filesystem that your > application is deployed to is not writeable. This behavior ensures the > security and scalability of your application. There are alternatives to > accessing the local file system, and re-writing accordingly should make > your app ready for GAE deployment. You may gather more related detail from > the "Reading and Writing Files" documentation page. [2] > > > [1] > https://cloud.google.com/appengine/docs/standard/python/getting-started/deploying-the-application > > [2] https://cloud.google.com/appengine/docs/standard/php/googlestorage/ > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0151c354-a478-499f-9411-64d1e52733ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
