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

update tutorials #190

Closed
wants to merge 1 commit into from
Closed

Conversation

plebhash
Copy link
Collaborator

@plebhash plebhash commented Jan 22, 2024

Copy link

netlify bot commented Jan 22, 2024

Deploy Preview for startling-capybara-2231ea ready!

Name Link
🔨 Latest commit ca0dcfe
🔍 Latest deploy log https://app.netlify.com/sites/startling-capybara-2231ea/deploys/65aec287c808580008140e29
😎 Deploy Preview https://deploy-preview-190--startling-capybara-2231ea.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@pavlenex
Copy link
Collaborator

pavlenex commented Jan 23, 2024

I yet have to dig deep into reviewing the docs, but at the first glance it seems too detailed. Should we optimize for what we have in Google Docs already? As our goal for quick start is to allow anyone to test SV2 quickly.

  1. Run hosted setup
  2. Run all roles

And just mention options for configuration, I was under impression we'll just port over entire Google Doc here and nuke anything else we have as currently this wall of text does seem a bit overwhelming.

@plebhash
Copy link
Collaborator Author

plebhash commented Jan 23, 2024

I yet have to dig deep into reviewing the docs, but at the first glance it seems too detailed. Should we optimize for what we have in Google Docs already? As our goal for quick start is to allow anyone to test SV2 quickly.

  1. Run hosted setup
  2. Run all roles

And just mention options for configuration, I was under impression we'll just port over entire Google Doc here and nuke anything else we have as currently this wall of text does seem a bit overwhelming.

indeed, I went through what we currently have (mostly focused on Config C and D) and updated it.
but if the team agrees I can also just port over the Google Docs instructions over here.

@GitGab19 @Fi3 wdyt?

@plebhash
Copy link
Collaborator Author

plebhash commented Jan 23, 2024

or also @pavlenex if you want, feel free to open a new PR going in this different direction, whatever you guys think is best

@GitGab19
Copy link
Collaborator

I yet have to dig deep into reviewing the docs, but at the first glance it seems too detailed. Should we optimize for what we have in Google Docs already? As our goal for quick start is to allow anyone to test SV2 quickly.

  1. Run hosted setup
  2. Run all roles

And just mention options for configuration, I was under impression we'll just port over entire Google Doc here and nuke anything else we have as currently this wall of text does seem a bit overwhelming.

indeed, I went through what we currently have (mostly focused on Config C and D) and updated it. but if the team agrees I can also just port over the Google Docs instructions over here.

@GitGab19 @Fi3 wdyt?

I agree with @pavlenex, now I would optimize what we have on the google doc as well.
It puts the focus on what we need to test more

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