highlight demo users

This commit is contained in:
Willy Kloucek
2021-04-12 18:41:16 +02:00
parent 9b95e9b119
commit a05b463069
7 changed files with 35 additions and 25 deletions

View File

@@ -11,7 +11,7 @@ geekdocCollapseSection: true
{{< toc >}}
## Deployments scenarios and examples
This section handles deployments and operations for admins and people who are interested in how versatile oCIS is. If you want to just try oCIS you may also follow [Getting started]({{< ref "../getting-started.md" >}}).
This section handles deployments and operations for admins and people who are interested in how versatile oCIS is. If you want to just try oCIS you may also follow [Getting started]({{< ref "../getting-started" >}}).
### Setup oCIS on your server
oCIS deployments are super simple, yet there are many configurations possible for advanced setups.

View File

@@ -18,7 +18,7 @@ The configuration for the continuous deployment can be found in the [oCIS reposi
# oCIS with Traefik
Credentials:
- oCIS: see [default demo users]({{< ref "../getting-started.md#login-to-owncloud-web" >}})
- oCIS: see [default demo users]({{< ref "../getting-started#login-to-owncloud-web" >}})
## Latest
@@ -31,7 +31,7 @@ Credentials:
# oCIS with Keycloak
Credentials:
- oCIS: see [default demo users]({{< ref "../getting-started.md#login-to-owncloud-web" >}})
- oCIS: see [default demo users]({{< ref "../getting-started#login-to-owncloud-web" >}})
- Keycloak:
- username: admin
- password: admin
@@ -49,7 +49,7 @@ Credentials:
# oCIS with CS3 users
Credentials:
- oCIS: see [default demo users]({{< ref "../getting-started.md#login-to-owncloud-web" >}})
- oCIS: see [default demo users]({{< ref "../getting-started#login-to-owncloud-web" >}})
- LDAP admin:
- username: cn=admin,dc=owncloud,dc=com
- password: admin

View File

@@ -120,7 +120,7 @@ See also [example server setup]({{< ref "preparing_server.md" >}})
* You now can visit oCIS, Keycloak and Traefik dashboard on your configured domains
## Local setup
For a more simple local ocis setup see [Getting started]({{< ref "../getting-started.md" >}})
For a more simple local ocis setup see [Getting started]({{< ref "../getting-started" >}})
This docker stack can also be run locally. One downside is that Traefik can not obtain valid SSL certificates and therefore will create self signed ones. This means that your browser will show scary warnings. Another downside is that you can not point DNS entries to your localhost. So you have to add static host entries to your computer.

View File

@@ -95,7 +95,7 @@ See also [example server setup]({{< ref "preparing_server.md" >}})
* You now can visit oCIS and Traefik dashboard on your configured domains
## Local setup
For a more simple local ocis setup see [Getting started]({{< ref "../getting-started.md" >}})
For a more simple local ocis setup see [Getting started]({{< ref "../getting-started" >}})
This docker stack can also be run locally. One downside is that Traefik can not obtain valid SSL certificates and therefore will create self signed ones. This means that your browser will show scary warnings. Another downside is that you can not point DNS entries to your localhost. So you have to add static host entries to your computer.
@@ -109,4 +109,4 @@ After that you're ready to start the application stack:
`docker-compose up -d`
Open https://ocis.owncloud.test in your browser and accept the invalid certificate warning. You now can login to oCIS with the default users, which also can be found here: [Getting started]({{< ref "../getting-started.md#login-to-ocis-web" >}})
Open https://ocis.owncloud.test in your browser and accept the invalid certificate warning. You now can login to oCIS with the default users, which also can be found here: [Getting started]({{< ref "../getting-started#login-to-ocis-web" >}})

View File

@@ -103,7 +103,7 @@ See also [example server setup]({{< ref "preparing_server.md" >}})
## Local setup
For a more simple local ocis setup see [Getting started]({{< ref "../getting-started.md" >}})
For a more simple local ocis setup see [Getting started]({{< ref "../getting-started" >}})
This docker stack can also be run locally. One downside is that Traefik can not obtain valid SSL certificates and therefore will create self signed ones. This means that your browser will show scary warnings. Another downside is that you can not point DNS entries to your localhost. So you have to add static host entries to your computer.

View File

@@ -3,8 +3,8 @@ title: "Getting Started"
date: 2020-02-27T20:35:00+01:00
weight: 0
geekdocRepo: https://github.com/owncloud/ocis
geekdocEditPath: edit/master/docs/ocis
geekdocFilePath: getting-started.md
geekdocEditPath: edit/master/docs/ocis/getting-started
geekdocFilePath: _index.md
---
{{< toc >}}
@@ -13,7 +13,7 @@ geekdocFilePath: getting-started.md
We are distributing oCIS as binaries and Docker images.
You can find more deployment examples in the [deployment section]({{< ref "./deployment/_index.md" >}}).
You can find more deployment examples in the [deployment section]({{< ref "../deployment/_index.md" >}}).
### Binaries
You can find the latest official release of oCIS at [our download mirror](https://download.owncloud.com/ocis/ocis/) or on [GitHub](https://github.com/owncloud/ocis/releases).
@@ -55,23 +55,11 @@ docker run --rm -ti -p 9200:9200 owncloud/ocis
### Login to ownCloud Web
Open [https://localhost:9200](https://localhost:9200) and login using one of the demo accounts:
```console
einstein:relativity
marie:radioactivity
richard:superfluidity
```
There are admin demo accounts:
```console
moss:vista
admin:admin
```
Open [https://localhost:9200](https://localhost:9200) and [login using one of the demo accounts]({{< ref "./demo-users" >}}).
### Basic Management Commands
The oCIS single binary contains multiple extensions and the `ocis` command helps you to manage them. You already used `ocis server` to run all available extensions in the [Run oCIS]({{< relref "#run-ocis" >}}) section. We now will show you some more management commands, which you may also explore by typing `ocis --help` or going to the [docs]({{< relref "configuration.md" >}}).
The oCIS single binary contains multiple extensions and the `ocis` command helps you to manage them. You already used `ocis server` to run all available extensions in the [Run oCIS]({{< relref "#run-ocis" >}}) section. We now will show you some more management commands, which you may also explore by typing `ocis --help` or going to the [docs]({{< relref "../configuration.md" >}}).
To start oCIS server:

View File

@@ -0,0 +1,22 @@
---
title: "Demo Users"
date: 2020-02-27T20:35:00+01:00
weight: 0
geekdocRepo: https://github.com/owncloud/ocis
geekdocEditPath: edit/master/docs/ocis/getting-started
geekdocFilePath: demo-users.md
---
As long as oCIS is released as [technology preview]({{< ref "../release_roadmap#release_roadmap" >}}) it will come with default demo users. These enable you to do quick testing and developing.
Following users are available in the demo set:
| username | password | email | role | groups |
| -------- | ------------- | -------------------- | ----- | ----------------------------------------------------------------------- |
| admin | admin | admin@example.org | admin | users |
| einstein | relativity | einstein@example.org | user | users, philosophy-haters, physics-lovers, sailing-lovers, violin-haters |
| marie | radioactivity | marie@example.org | user | users, physics-lovers, polonium-lovers, radium-lovers |
| moss | vista | moss@example.org | admin | users |
| richard | superfluidity | richard@example.org | user | users, philosophy-haters, physics-lovers, quantum-lovers |
You may also want to run oCIS with only your custom users by [deleting the demo users]({{< ref "../deployment/_index.md#delete-demo-users" >}}).