update kickstart to include theme and silicon user #32
Conversation
| "asymmetricKeyId": "#{UUID()}", | ||
| "clientSecret": "this_really_should_be_a_long_random_alphanumeric_value_but_this_still_works_dont_use_this_in_prod", | ||
| "applicationId": "c2aeeb1e-65cd-43c5-9326-02dce5e03705", |
There was a problem hiding this comment.
I was wandering what the groups opinion on this was. Should we all share the same sample application or should each quickstart have it's own application. I can see pros and cons of both.
There was a problem hiding this comment.
As kickstart will only be read when setting up a new instance, I think we can use the same Id to make things easier.
But I'd love if we had a feature to import a kickstart file into an existing instance, which would require us to have specific Ids for each application.
There was a problem hiding this comment.
I agree with @vcampitelli . I don't expect anyone to run multiple quickstart applications off the same FusionAuth server.
We do have an open issue on importing a kickstart file into an existing instance.
| "asymmetricKeyId": "#{UUID()}", | ||
| "clientSecret": "this_really_should_be_a_long_random_alphanumeric_value_but_this_still_works_dont_use_this_in_prod", |
There was a problem hiding this comment.
I don't mind leaving this as the same for all sample apps. Good to have something awkward there to people know to change.
| @@ -40,7 +41,7 @@ | |||
| "name": "ExampleNodeApp", | |||
| "oauthConfiguration" : { | |||
| "authorizedRedirectURLs": ["http://localhost:3000/oauth-callback"], | |||
| "logoutURL": "http://localhost:4200/", | |||
| "logoutURL": "http://localhost:3000/", | |||
There was a problem hiding this comment.
I like the quickstarts not being on port 3000 as that is where the astro site wants to run. This could be moved to a variable and then replaced here and line 43 too.
| @@ -1,15 +1,16 @@ | |||
| { | |||
| "variables": { | |||
There was a problem hiding this comment.
would like to see a variable for applicationName too unless we are going to create one generic "Sample App"
|
This makes sense to me. One thing to consider is to not commit the CSS file to this repo but to pull it from here: https://github.com/fusionauth/fusionauth-example-themes when creating a new quickstart. |
|
@alex-fusionauth what is left to do on this? |
| @@ -1,15 +1,16 @@ | |||
| { | |||
| "variables": { | |||
| "applicationId": "E9FDB985-9173-4E01-9D73-AC2D60D1DC8E", | |||
There was a problem hiding this comment.
We want this to be the same value.
| @@ -40,7 +41,7 @@ | |||
| "name": "ExampleNodeApp", | |||
| "oauthConfiguration" : { | |||
| "authorizedRedirectURLs": ["http://localhost:3000/oauth-callback"], | |||
| "logoutURL": "http://localhost:4200/", | |||
There was a problem hiding this comment.
Maybe we should have logoutURL be a variable?
I think we should all probably review and agree on what this looks like, but it is a start.
Each app still needs specific updates based on that app, for instance in the Next.js I still used the HTML/CSS from the template but had to move them into something like
app/src/page.tsx. But it keeps a nice look and feel with the theme for the login within FusionAuth.