Skip to content
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

[Deployment] One-click deployment options in README.md or docs #6568

Open
michaelstingl opened this issue Jun 20, 2023 · 6 comments
Open

[Deployment] One-click deployment options in README.md or docs #6568

michaelstingl opened this issue Jun 20, 2023 · 6 comments
Labels
Category:Enhancement Add new functionality

Comments

@michaelstingl
Copy link
Contributor

michaelstingl commented Jun 20, 2023

Is your feature request related to a problem? Please describe.

oCIS setup has some complexity, but could be much simpler in standardised environments.

Describe the solution you'd like

Prominent self-hosting buttons to fire up instances on public cloud services could lower the entry barriers.

Examples

/cc @hodyroff FYI

@michaelstingl michaelstingl changed the title [Deployment] On-click deployment options in README.md or docs [Deployment] One-click deployment options in README.md or docs Jun 20, 2023
@tbsbdr
Copy link

tbsbdr commented Jun 20, 2023

.. services could to lower the entry ..

@mmattel
Copy link
Contributor

mmattel commented Jun 20, 2023

We can do a setup documentation based on a standardised environment - but that term needs to be defined very precisely before we can go on. Just one topic out of the many has variaties that will cause headaches when using the term standardized :
local IDM vs Keycloak vs AD vs Azure vs Athelia vs authentik...

If there is focus on describing definied standardized setups (note the plural !), which needs highly skilled ressources, we can achive this - that definitely supports business.

Note that the ocis admin docs are the only location to go for such content.

@michaelstingl
Copy link
Contributor Author

michaelstingl commented Jun 20, 2023

We can do a setup documentation based on a standardised environment

What the public cloud provider offers…

CleanShot 2023-06-20 at 19 03 36

Should do the same as our easiest CD example:

After default setup, you get something running:

With Elest.io, you get $20 free credits that you can use to play with for 7 days. Try yourself… (or $250 free credits when you join via try.digitalocean.com/elestio )

If there is focus on describing definied standardized setups (note the plural !), which needs highly skilled ressources, we can achive this - that definitely supports business.

  • ONE standardized setup
  • MULTIPLE standardized environments (public + private cloud/SaaS providers)

@pascalwengerter
Copy link
Contributor

I quite like the idea but wonder how we'd handle IDM_ADMIN_PASSWORD without "publicly hardcoding it"?

@michaelstingl
Copy link
Contributor Author

I quite like the idea but wonder how we'd handle IDM_ADMIN_PASSWORD without "publicly hardcoding it"?

In my example, elest.io handles it. It generates a .env files with the credentials, and they can be revealed in the elest.io web UI. I encourage you all to try it yourselves.

@stale
Copy link

stale bot commented Sep 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status:Stale label Sep 16, 2023
@micbar micbar added the Category:Enhancement Add new functionality label Sep 18, 2023
@stale stale bot removed the Status:Stale label Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:Enhancement Add new functionality
Projects
None yet
Development

No branches or pull requests

5 participants