-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 0.0.1 #8
Comments
Added a list of what I think the must haves are for an mvp. |
I think the plugin explorer is probably safe to push for a future release. |
Added "Design" to the list. |
Well, per previous conversations the design was supposed to just follow the current console. I'd think if we just mirror as closely as we can while leveraging material design, we'll be good.. so not sure if that's something we need since it's more or less already drawn out. |
I just mean we have to match that localize that HTML/CSS, which will no doubt take some work! |
My bad! You are correct sir. |
@jgeewax is there a way to get access to the source style and markup files for the console? |
Do we need those? |
I thought it would help us and people who tweak the console to have the originals. You don't think so? |
Well, I was thinking if we leveraged material design everywhere our markup wouldn't be 1:1 with the current console (unless they use it too?) |
Ah, alright. So we need to recreate everything and just use the dev tools to match the little details? |
That's where I was headed, what are your thoughts on that? |
If you're good with that and you don't think source files will help, no objections here. |
Yea, also the UI will be changing so let's not go for identical and instead
focus on "looks good enough".
What do you guys think about focusing on the container, and then either a
web hosting UI (for the people who want to use GCS to host static content)
and then maybe a GCE UI that looks and feels more like Digital Ocean...?
|
Are these plug-ins? I think that sounds pretty cool. But, I'm starting to think we should host the container and deal with handling auth and persisting user config ourselves. Especially when I think of the "GCS to host static content" idea-- if the cost of getting a super easy to use UI is "download and host this control panel thing and install whatever plug-ins you want yourself," I start to lose interest and think about just using Digital Ocean instead. From the perspective of someone who just wants to get a site on GCP, I probably don't care about the flexibility of tweaking the CP's look and feel too much. TLDR: 👍 OSS plug-ins to access my GCP stuff, 👎 "host it yourself" - is there any way we can just host this stuff? |
I'm all for us having a hosted version (just some statically served files
on GCS), but if you want to do it yourself you should be able to... Fair?
And yes - those would be plug-ins for sure.
|
Yeah, that should work. The container will still be OSS so its extensible, and we'll just run a hosted version. Will serve as a nice live demo as well. |
@jgeewax I opened this issue about a problem I'm having using the official client side JS library with Resource Manager (ideally we would use this to get the project's a user controls). I posted it on Saturday, so it's obviously not a big deal that there's no reply yet, but looking at the activity on the repo, there are a lot of issues that seem to go uncared for (the last closed issue was one in July and before that, January). Do you know of a better way to get quicker help for this problem? |
Potentially related to googleapis/google-cloud-node#864 ? |
I don't believe so. With the API explorer, I auth as myself. But with or without auth, trying to execute the API call returns a 404, which leads me to believe something is wrong either with the discovery doc or the way the API library parses it. |
I think it's the google api, I got around this by manually creating the request like so.. gapi.auth.authorize({
client_id: '288560394597-82lbmhf7077sl5bfp1ll4nnjbhi27etn.apps.googleusercontent.com',
scope: 'https://www.googleapis.com/auth/cloud-platform'
}).then(function() {
return gapi.auth.getToken().access_token;
}).then(function(token) {
return new Promise(function(resolve, reject) {
var xhr = new XMLHttpRequest();
xhr.onload = resolve;
xhr.onerror = reject;
xhr.open('GET', 'https://cloudresourcemanager.googleapis.com/v1beta1/projects');
xhr.setRequestHeader('Authorization', 'Bearer ' + token);
xhr.send();
});
}).then(function(response) {
console.log('something went right');
console.log(response);
}).then(null, function(err) {
console.log('something went wrong');
console.log(err);
}); So maybe instead of using that angular service, we'll have to make our own and leave it to the user to plug in the crap they need. |
Well, resource manager is the only one I've had issues with so far (granted, I've only tried that and Storage). Maybe we can just hack it like above to get the list of projects, then keep letting users use gapi? It's definitely the most convenient way to get to the APIs. |
That works for me! |
Nicely done by the way! |
Thanks! I'll turn you into a promise lover sure enough 😉 |
@callmehiphop everything you've done is beautiful :) |
hey thanks! I'm sure it'll all change 😆 |
@callmehiphop -- you've been leading the FE charge on this one. Can you plop down a list of the things required to have "something" ready for 2 weeks from now (9/25).
$window.transport
, but waiting on @callmehiphop for a more correct architecture there.package.json
schemaPlugin explorer(future)gcloud-static-web-host
The text was updated successfully, but these errors were encountered: