If you want to learn more about Cloud Shell, the marketing page is here: https://cloud.google.com/shell/
Cloud Shell is one of my favorite things about GCP. A lot of dev tools (Docker, Python/Go/Node/Ruby/Java/.Net, etc) are pre-installed, you can test "localhost" servers with the preview feature, there is a built in file editor (based on the open source Orion project), etc. And it's all free!
This link will directly open the shell in a full page, and I'm not sure it will work unless you have set up your GCP account before. It's really not designed to be opened this way, I recommend opening it from the GCP console and then making it full screen if your want.
Also note: Cloud Shell gives you a persistent 5GB /home Directory, but every other folder is reset after a while. If you want to add your own binaries, I'd recommend adding home to your path and installing them there.
If the instance is ephemeral, I need to manage everything in HOME and that's fine. For Python, that basically means using Virtualenv. That works fine at the moment for python 2.7, but 3.x on Debian requires the package python3-venv, which is not installed by default - and sure enough, it's missing in Cloud Shell.
It's a bit annoying having to apt-get install python3-venv every time. Any chance it could be preinstalled? It's such an essential tool for modern python development...
It's an annoyance specific to Debian and to this day I'm not sure I understand the rationale for splitting it out of the main python3 package.
Python 3.6.4 (default, Jan 28 2018, 00:39:17)
Type 'copyright', 'credits' or 'license' for more information
IPython 6.2.1 -- An enhanced Interactive Python. Type '?' for help.
In : from __future__ import braces
File "<ipython-input-1-6d5c5b2f0daf>", line 1
from __future__ import braces
SyntaxError: not a chance
In "6. Data Deletion" Google assures that data will be delete in a reasonable fashion upon request or on expiry of the term. Google reserves the right to share the data with other entities in "11.2 Information about Subprocessors" which are listed in . I assume that the data will also be deleted from the subprocessors. It is also stated that the function is explained, yet an exhaustive explanation is missing. The most informative I can find is that they "provide customer and technical support" besides some non-exclusive examples of activities.
Also, I see no part that ensures Google won't analyze the data, like for example to train neural networks. Could you point me to it?
Any idea why Apache and Gradle are installed in the root directory? Normally, these would be in `opt` or some such.
> any modifications that you made to it outside your $HOME are lost.
Anyway, not a huge deal, just a bit odd. And evoking my OCD: ...must...keep...clean...root.
The Cloud Shell is a Debian Stretch container, so it's easy to install packages as you will. If you want them to be persistent install them on your home folder and add the route to your env vars.
From one way of thinking, Apps Script is a lot like AWS Lambda; but from another way of thinking, Apps Script is more like OS automation workflows that happen to run in your cloud account rather than on your computer.
You don't have to be a "Gmail user".
Is that a T&C rule or a technical block? Because I'm in EMEA, not registered as a business, and it opened for me just fine.
GCP support did respond to my inquiry and they specified that it's the case in whole EMEA.
P.S I just tried and it appears they've added option to switch to "Individual". Great!
"In Russia, Google Cloud Platform services can be used only for business purposes. Warning: If the sole purpose for which you want to use Google Cloud Platform services has no potential economic benefit you should discontinue your use of the service"
It used to say the same thing about EU citizens for a while. The line about "no potential economic benefit" is pretty bizarre as far as far as I've seen...
>Warning: If the sole purpose for which you want to use Google Cloud Platform services has no potential economic benefit you should discontinue your use of the service"
To me this says: "Anything and everything can become a side project at any moment or be used to help support a business and therefore (in my opinion) everything can be thought of as a business or supporting a business. If there is no potential conceivable way to view anything you might ever do on the platform as conceivably pivoting into a startup or supporting a startup or any other business need in the future, or creating any economic (business) benefit then you should discontinue it. Everyone else can just say they might be a side project / pivot or be used as a business in the future, or used to support a business or otherwise produce value, since there is no way to show otherwise."
With this lens it makes perfect sense that if the SOLE purpose has NO potential (potential!!!) economic benefit (i.e. used to at least support a business or create value) then you should discontinue it. This warning applies basically to no one.
It's really an excellent sentence, I like it a lot.
$ find /opt/dotnet/ -name \*.sh
Haven't tried it and it may be against the conditions.
It has a docker0 network interface (among others)
That's for the dockerd which is running inside the ... VM?
The interesting thing is that the uptime and dmesg show that this system is not shared on the kernel level - if I were to guess, I'd say that Google allocates a real virtual machine with a tiny OS running Docker, starts the docker container inside this VM and then grants you webshell/ssh access to this Docker container.
But why the Docker setup when the machine is yours anyway?
$ docker pull hello-world
$ docker run hello-world
Hello from Docker!
This message shows that your installation appears to be working correctly.
But not Docker. More likely Google's own container tech which I'm pretty sure way predated Docker.
I am curious because we made a somewhat similar tool for conducting interviews but ours has collaboration too.
Has ssh, vim, tmux, and docker installed.
I'm guessing this is either a container itself or a Debian vm.
I'm still finding new things that are installed and useful.
I would find myself using it to QA docker compositions I write. The question is can I host from this instance?
(I work for Google Cloud)
"slashdotted?", or whatever the hackernews term for that is?
Cloud Shell is a "temporary" instance, really meant for interactive Dev/Admin work.
(I work for GCP)
"Thanks for signing up for the 12-month free trial.
We've given you $300 in free trial credit to spend. If you run out of credit, don't worry, you won't be billed until you give your permission."
[ed: and as mentioned above there are instances that don't consume any of those 300 credits]
The free trial is $300 for 12 months that you can spend on pretty much anything (I think there are some limits on GPUs due to abuse).
The free tier is free forever, no dollar limits or time limits. This includes the 24/7 f1-micro, 28 App Engine hours per day, Cloud Datastore, Firebase stuff, some Cloud Functions, etc.
I would like to test the throughput, measure uptime over a few months, and check how well it handles DDOS. I would configure 10x static IPv4 and IPv6 to make sure it does not impact anyone else.
I plan to setup a nginx serving a few static pages with a Round Robin DNS on a subdomain.
Basically the free tier subtracts the cost of a f1-micro from your monthly bill if you have at least one running.
Do you know if a f1-micro can cost more than $4 per month if it is used extensively? By that, I just mean 100% cpu usage, 100% of the 5Gb disk quota, with just 1 IPv4 and 1 IPv6.
I like the scalability, but I want my clients to know that their bill will not "fluctuate".
Cost-wise, $40 for 10 IPv4 is in the upper tier (some OVH resellers give you 16 IPv4 on some decent dedicated server) but for what I need (low latency), the wide geographic coverage could still make it worthwhile.
Neither was I, agreed! Thank you for sharing, now I can actually test a few services to see if it makes sense migrating some of our microservices (or probably better stated: nanoservices) to gCloud that are currently running on expensive bare metal (wasn't my call, I'm just trying to get us to modernize).
Also, fetching dependencies to a machine in a data center avoids bringing down the wifi in a class.
And even though the UI can be a bit sluggish at times i can’t say AWS was any better last time I used it
$ ruby --version
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux]
AWS Cloud9 lets me pay for a single big honkin ec2 that backs the IDE, has a better editor, browser ssh support—and has a built in option to suspend the “expensive” instance after 30 mins of inactivity.
I loved Cloud Shell but the inability to let me pay for a bigger backing instance or more storage is a real limitation. (One of my commonly worked on projects takes 25 mins to compile on a boost mode Cloud Shell instance, and operates on ~80GiB of data.) Cloud9 is at a real advantage here.
Whoever first integrates Atom, though (all of these seem to use Ace), I think will be the real winner.
Cloud Shell has Vim 8 installed, which you can use instead.
Except Cloud Shell has Boost Mode:
> Whoever first integrates Atom, though (all of these seem to use Ace), I think will be the real winner.
Google's is based on Orion, not Ace.