Skip to content

Conversation

Frzk
Copy link
Contributor

@Frzk Frzk commented Aug 13, 2025

Related to #2278
Related to #3036
Related to #3037

  • Update all the "Getting Started With..." guides (ModSecurity, Grafana, ELK stack, SonarQube, Metabase and WordPress)
  • Add one for n8n

@Frzk Frzk self-assigned this Aug 13, 2025

[![Deploy](https://cdn.scalingo.com/deploy/button.svg)](https://dashboard.scalingo.com/deploy?source=https://github.com/Scalingo/grafana-scalingo)
- While Grafana's officially recommends to have a minimum of 512MB of RAM, we
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to say why?


Then, clone our repository and add the Scalingo git remote:
### Using our One-Click Deploy Button
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not just call it One-Click deploy?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure to fully understand your question, nor to follow where you want to go...So my answer is : because we provide a button to click.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's more to homogeneize the name around it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@benjaminach: any thoughts about this naming?

Copy link
Contributor

@benjaminach benjaminach Sep 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hum, I am a bit confused, because nothing in the button indicates that it will be deployed as a “One Click” something. Is that the sole purpose of this button?

For now, I think I would give it a more generic title, like "Using the Deploy to Scalingo button"

Ok, in the context of the page, we understand that this is the button to click.

6. After a few seconds, your Grafana instance is finally up and running!


## Updating
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe talk about how to update the one click no ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no easy way to update after using the one-click deploy button.
But I'm opened to suggestions.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah you are right, but maybe told them to do some backup if they use a database for example and the dasboard ( for grafana)

@Frzk Frzk marked this pull request as ready for review September 3, 2025 14:03
@Frzk Frzk requested a review from benjaminach September 3, 2025 14:03
[db-postgresql]: https://www.scalingo.com/databases/postgresql

[dashboard]: https://dashboard.scalingo.com
[one-click]: https://dashboard.scalingo.com/deploy?source=https://github.com/Scalingo/grafana-scalingo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[one-click]: https://dashboard.scalingo.com/deploy?source=https://github.com/Scalingo/grafana-scalingo
[one-click]: https://dashboard.scalingo.com/create/app?source=https://github.com/Scalingo/kibana-scalingo

Shouldn't it be this link?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed the links in 0b15945

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants