Using Google Cloud for a couple days now and this is vastly more difficult than working with Site5 or HostGator. I can develop a fully functional site in HTML, PHP, and JavaScript and host on these simpler platforms. The sites I want to develop can outgrow the boots over there, so clearly Google is a good solution. On top of learning all that code in that past, I have to learn some Linux commands, done, now I have to learn some permission work in Linux, done, after that I have to learn Google interface, done. From there things get increasingly difficult in ways that should be avoidable.
- Mounting a disk inside var will clash .ssh keys locking up the VM.
Now I have to be an Apache administrator or I have to hire an expert to teach my server to see files outside var in mnt/disks, or some other directory.
Solution: Could not .ssh keys be given some kind of namespace? Or be placed in a different location? Mounting persistent disks just outside root would have been infinitely easier.
Okay, so I tried a windows VM so I could test out IIS server. Instantly I could not set password. So I need to add a permission. Now you can’t add permissions to the existing owner role, which is ridiculous. I already have an owner role created by Google. I should not have to make another role to muddy the experience. So I have to add new owner role. And when it’s done how do I incorporate it? When I SSH in console is it always using that role? What a mess of learning.
Solution: Let me add whatever permissions I want to the owner role I’m already using for everything.
Now I want to try buckets out to solve the problem. I download the SDK for PHP. Everything works fine with the form, when I incorporate jQuery and send as FormData everything is infinitely harder yet again. There’s a CORS error when telling it I expect XML back, and 403 (or similar, the permissions error) error when I tell it jsonp. So who is messing up my entry: Google or jQuery? Is it something in Cloud or one of the 4 jQuery settings, including their new CORS key attribute. Which error do I tackle? Both have seemingly logical solutions.
On top of that lets just throw in simple and pre-flight. And make a page of logic to even begin to understand it. Who do I get support from: Google or jQuery? You guys aren’t even the same company. This is ridiculous. Is there even inside support over there, with GCS knowledge?
It's learning after learning, without getting ahead in development. This is like if online banking wanted a retina scan, finger prints, card number, password, sin number, and .ssh key, to let me into my account. Who by the way just want a card number and password.
This CORS stuff is a common frig for a lot of people, just Google people asking for help and solutions. I already added my cors.json info to the bucket. Not even Stripe asks for this kind of flaming hoop work to use their systems for money!
Solution:
Give us a “secure enough” entry and let this CORS stuff be available for the pros, who need to protect hard core data. Why not more .ssh, or AES cipher, Or maybe the json cors settings I made to the bucket could be used with a simplified CORS call of some kind. That way jQuery sending FormData can’t mess up. I just had the PHP SDK sign two cryptic entries for the form, that should have been good enough, since a console download was included! If anyone can get my json credentials file, they can do in jQuery whatever you’re trying to get me to do.
Good luck figuring all this out with forum help, because if you don’t, you don’t get your site. I guess I can just use the form with a spinner. One minute a progress bar was simple, now it’s extremely hard, to impossible.
LinkedIn
Twitter
