-
Notifications
You must be signed in to change notification settings - Fork 3
add Nextcloud to Application Deployment Demos #210
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Somewhat the same nitpick as with the other UI screenshot.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. done |
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,128 @@ | ||||||||
| = Deploy https://products.vshn.ch/appcat/nextcloud.html[VSHNNextcloud] to {product} | ||||||||
|
|
||||||||
| image:logos/nextcloud.svg[role="related thumb right",alt="Service logo nextcloud",width=120,height=120] This tutorial explains how to run https://nextcloud.com/[Nextcloud] with link:++https://products.vshn.ch/appcat/nextcloud.html[VSHNNextcloud]++[VSHNNextcloud] on {product} using the pipeline from https://www.vshn.ch/en/solutions/appflow/[Appflow]. | ||||||||
|
|
||||||||
| == Requirements | ||||||||
|
|
||||||||
| This tutorial requires an {product}, a https://github.com[GitHub] account. | ||||||||
martini-source marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||
|
|
||||||||
| == Add the https://products.vshn.ch/appcat/index.html[VSHN Application Catalog] claim | ||||||||
|
|
||||||||
| To provision Nextcloud, we need a https://products.vshn.ch/appcat/nextcloud.html[VSHNNextcloud] claim. The documentation for VSHNNextcloud can be found here: https://docs.appcat.ch/vshn-managed/nextcloud/index.html[Nextcloud by VSHN]. | ||||||||
|
||||||||
| To provision Nextcloud, we need a https://products.vshn.ch/appcat/nextcloud.html[VSHNNextcloud] claim. The documentation for VSHNNextcloud can be found here: https://docs.appcat.ch/vshn-managed/nextcloud/index.html[Nextcloud by VSHN]. | |
| To provision Nextcloud, we need a https://products.vshn.ch/appcat/nextcloud.html[VSHNNextcloud] claim. | |
| The documentation for VSHNNextcloud can be found at https://docs.appcat.ch/vshn-managed/nextcloud/index.html[Nextcloud by VSHN]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does https://docs.appcat.ch/references/argocd.html also apply if the claim is wrapped in a helm chart? Never tested that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We let helm try to delete the resources in the deployments we did until now.
The helm uninstall fails in this case because of the deletion protection.
If you want to uninstall a helm chart with appcat claims you must disable the deletion protection before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But then the app remains in an unsynced state? Because it tries to delete the claim but can't? It also sounds a bit dangerous having it hang in limbo the whole time.
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please keep the sources at one sentence per line.
| If you are a VSHN customer, you can generate the pipeline to deploy Nextcloud in | |
| xref:#appflow-helm[AppFlow]. | |
| If you are a VSHN customer, you can generate the pipeline to deploy Nextcloud in xref:#appflow-helm[AppFlow]. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it makes sense to link to a particular APPUiO zone here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have an APPUiO Account you have access to both clusters, not?
What would be your suggestion?
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is probably your token :) -- should be expired by now I assume.
You want the following link here: https://oauth-openshift.apps.cloudscale-lpg-2.appuio.cloud/oauth/token/request
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uupsi, thank you.
The token is as get parameter in there and not determined via the authentication.
I rotated the token.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replaced with web login
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not just oc login --web --server https://api.<zone>.appuio.cloud:6443? That should pop up a login screen or immediately fetch a token via local browser integration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just as info: Here is another way documented: https://portal.appuio.cloud/kubeconfig
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BacLuc The linked docs are about connecting to the APPUiO control API (which is also just a kubernetes API). Not to an actual APPUiO cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just as info: Here is another way documented: https://portal.appuio.cloud/kubeconfig
That has nothing to do with accessing a zone, that's for accessing the APPUiO Control API directly via kubectl instead of via portal.appuio.cloud
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replaced with oc login --web
martini-source marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
martini-source marked this conversation as resolved.
Show resolved
Hide resolved
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure whether this is a good fit for the APPUiO end user docs (since APPUiO as a product encourages self-service via K8s API). Currently, users who signed up for APPUiO via social login / self sign-up don't even have access to control.vshn.net. IMO this would make more sense somewhere in the VSHN AppFlow user documentation.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See other comment. For users with AppFlow it is way more convenient. Customers who don't have access to AppFlow see the feature and might want to buy it. We will keep the AppFlow docs here. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| [#appflow-helm] | ||
| == Create application and environment with link:++https://www.vshn.ch/en/solutions/appflow/[Appflow]++[AppFlow] | ||
|
||
|
|
||
| Navigate to https://control.vshn.net/appflow/apps[AppFlow] on the https://control.vshn.net/[VSHN Portal] and click on `Create App with Environment`. | ||
|
|
||
| .AppFlow create App | ||
| image::how-to/appflow/appflow-create-app.png[AppFlow create App] | ||
|
|
||
| Then you should see the created application with its environment, in this case, `prod`. | ||
|
|
||
| .AppFlow download pipeline and CI variables | ||
| image::how-to/appflow/appflow-download-pipeline-secrets.png[AppFlow setup CI] | ||
| <1> Download GitHub workflow | ||
| <2> Show CI variables | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If something in the UI changes this is outdated.
I would explain the necessary configuration options along with sensible default values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done