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

A few more improvements to the README.md #13

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

rpkoller
Copy link

@rpkoller rpkoller commented Mar 19, 2024

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:

  • added a TOC and structured the entire document with headlines
  • untwine the long codeblock at the beginning and move the different parts into the appropriate sections
  • tried to make it clear nothing should be installed (required) with composer like for example drush (therefore the warning box to make it extra clear)
  • added the omit the database container flag since the addon is using SQLite (to save a few megabyte but at the same time to help the user to understand how the add is working and what database is used - which is also relevant in case someone wants to drop the database tables in case one is working on a patch in the context of the drupal installer).

plus i've added the suggestions @rfay made over on the old PR into this one

@rpkoller rpkoller marked this pull request as ready for review March 19, 2024 14:15
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link

@T-Fletcher T-Fletcher left a comment

Choose a reason for hiding this comment

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

Looks like #17 was merged in, you may want to rebase this so we don't double up on changes. In particular, @rfay's line about running DDEV with preset flags for overrides, php version etc.

Given my #16 was getting messy, I'm happy to work on this one instead as we're working towards the same goal.

@rpkoller rpkoller force-pushed the 20240319-rpkoller-readme-improvement branch from 358c6b3 to 93a1cb9 Compare March 27, 2024 14:52
@rpkoller
Copy link
Author

rpkoller commented Mar 27, 2024

Looks like #17 was merged in, you may want to rebase this so we don't double up on changes. In particular, @rfay's line about running DDEV with preset flags for overrides, php version etc.

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.

Given my #16 was getting messy, I'm happy to work on this one instead as we're working towards the same goal.

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:

I think that the 3-4 contributors trying to sort things out in the justafish repo should just sit down and collaborate. Slack channel for that might not be a bad idea. Competing PRs are just going to waste justafish’s time and energy

that was the reason behind simes posting (#22). so you are more than welcome to join the discussion on the newly created channel.

@T-Fletcher
Copy link

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?

@rfay
Copy link
Contributor

rfay commented Mar 27, 2024

See

@T-Fletcher

Copy link
Contributor

@rfay rfay left a 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.

README.md Outdated Show resolved Hide resolved

```
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
Copy link
Contributor

Choose a reason for hiding this comment

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

This really shouldn't be needed any more, if we do a ddev config --update. Also, the @simesy #23 handles this right?

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
ddev corepack enable
ddev exec corepack enable

Copy link
Author

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

Copy link
Author

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.

Copy link
Contributor

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`.
Copy link
Contributor

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.

Suggested change
Because `ddev-drupal-core-dev` is using SQLite the database container could be omitted on `ddev config --project-type=drupal10 --omit-containers=db`.

Copy link
Author

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.

Copy link
Contributor

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.

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@rfay rfay left a 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
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
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`.
Copy link
Contributor

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.

Copy link
Contributor

@rfay rfay left a 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.

@rpkoller rpkoller force-pushed the 20240319-rpkoller-readme-improvement branch from c393e34 to 261a374 Compare April 29, 2024 15:02
@rpkoller rpkoller force-pushed the 20240319-rpkoller-readme-improvement branch from 261a374 to c26b7e8 Compare April 30, 2024 12:46
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