-
Notifications
You must be signed in to change notification settings - Fork 11
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
A few more improvements to the README.md #13
base: main
Are you sure you want to change the base?
A few more improvements to the README.md #13
Conversation
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.
358c6b3
to
93a1cb9
Compare
thank you, i've rebased my branch against upstream/main now. i was under the impression since the github ui showed that the branch has no conflicts with the base branch it wouldn't be necessary. but definitely the better and cleaner choice.
i think we shouldnt expand the scope and pack more things into this PR. I would keep this PR about simply restructuring the README to improve hopefully readability and clarity. The PR you have started is more about functionality and that the quickstart guide runs through without any stumbling blocks. And in regards of the continuing problems #16 and also #20 @simesy tried to fix alongside the changes in the upcoming version 1.23.0 of DDEV https://github.com/ddev/ddev/releases/tag/v1.23.0-alpha1 @rfay suggested in a conversation on slack to do the following:
that was the reason behind simes posting (#22). so you are more than welcome to join the discussion on the newly created channel. |
Sounds like a smart approach, I agree with trying to keep functionality vs readability separate but note this can be messy when we are working on the same files via separate PRs. What's the Slack channel called? |
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.
Thanks for this, it's going to be great.
Minor suggestions. Should go in ASAP.
|
||
``` | ||
git clone https://git.drupalcode.org/project/drupal.git drupal | ||
cd drupal | ||
ddev config --project-type=drupal10 | ||
ddev config --omit-containers=db --disable-settings-management | ||
ddev start | ||
ddev corepack enable |
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.
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.
ddev corepack enable | |
ddev exec corepack enable |
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.
as i've mentioned on discord. ddev config --omit-containers=db --disable-settings-management
is the exact line used on @simesy's PR. the only overlapping line. therefore i've adjusted it here to avoid conflicts and hassle. and i think those two flags are still needed. for one to avoid the db containers plus to disable the settings management. the rest is done bei config --update
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.
in regards your corepack suggestion. all the quickstart commands i havent bothered. all of those are taken care of in simes PR. and that corepack line is obsolete and not necessary anymore. config --update takes care of 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.
Oh, that PR removes this line? OK. But at least it could be correct. There isn't a ddev corepack
anywhere. All good.
README.md
Outdated
ddev start | ||
ddev corepack enable | ||
ddev get justafish/ddev-drupal-core-dev | ||
ddev restart | ||
ddev composer install | ||
```` | ||
Because `ddev-drupal-core-dev` is using SQLite the database container could be omitted on `ddev config --project-type=drupal10 --omit-containers=db`. |
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 has already been done above.
Because `ddev-drupal-core-dev` is using SQLite the database container could be omitted on `ddev config --project-type=drupal10 --omit-containers=db`. |
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.
In this comment I try to explain "why" the --omit-container
flag was actually used.
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.
IMO it would be better to do that in a comment above the command. Here it's out of context.
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.
Noticed problem with ddev corepack
, which isn't a thing. I don't think we even have to do this when the other PR goes in.
|
||
``` | ||
git clone https://git.drupalcode.org/project/drupal.git drupal | ||
cd drupal | ||
ddev config --project-type=drupal10 | ||
ddev config --omit-containers=db --disable-settings-management | ||
ddev start | ||
ddev corepack enable |
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.
ddev corepack enable | |
ddev exec corepack enable |
README.md
Outdated
ddev start | ||
ddev corepack enable | ||
ddev get justafish/ddev-drupal-core-dev | ||
ddev restart | ||
ddev composer install | ||
```` | ||
Because `ddev-drupal-core-dev` is using SQLite the database container could be omitted on `ddev config --project-type=drupal10 --omit-containers=db`. |
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.
IMO it would be better to do that in a comment above the command. Here it's out of context.
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.
Thanks, it should be fine! I'd rather have ddev exec corepack enable
if it's going to be there at all but we can wait for that.
c393e34
to
261a374
Compare
Co-authored-by: Randy Fay <[email protected]>
Co-authored-by: Randy Fay <[email protected]>
Co-authored-by: Randy Fay <[email protected]>
Co-authored-by: Randy Fay <[email protected]>
sdc went stable and the given sdc directory contains only a single yaml file. no tests no nothing anymore. Co-authored-by: Randy Fay <[email protected]>
…to the quickstart as a comment
261a374
to
c26b7e8
Compare
… drupal uninstall
I've already created a draft before (#9) but thanks to my "excellent" git and github skills something went wrong when i tried to sync my branch with the latest changes when randys PR went in. I've simply created a new PR now, that was faster incorporating my suggested changes i've done locally so far.
and again at first thank you for creating that excellent add-on! and as a disclaimer i am not a developer just a regular ddev user who was just used to a composer patches based workflow for testing issues on drupal.org. when i first tried the add-on i ran into a few stepping blocks since it is following a slightly different paradigm (i've expecting the folder structure with web as the docroot and i've installed drush wondering why i haven't had a
git status
without any changes). one or two weeks ago i've also noticed a support request on the drupal slack by someone trying to get the add-on work (who had basically the same issues like me). so based on my own experience as well as the details i've learned during the conversation on slack i've tried to come up with a few improvements to the README.md:plus i've added the suggestions @rfay made over on the old PR into this one