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

README update of Tomcat environment setup. #1607

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

IgorBia
Copy link

@IgorBia IgorBia commented Aug 27, 2024

Changed:

  • "entS" -> "comS" (entS does not exist),
  • Improved visibility of important text in xyz apostrophes by bolding,
  • Reedited paragrahs about building projects to make it more easy to read.

Added:

  • Numbering headings to make it more like step-by-step guide,
  • Xml formatting,
  • Helpful links point.

@CLAassistant
Copy link

CLAassistant commented Aug 27, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@dsibilio dsibilio 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 your contribution. While I appreciate your efforts in trying to improve this documentation, I don't see a great benefit from the changes as they are currently presented.

I stopped my review half-way through, please go ahead and either:

  • vastly refactor the PR so that only minimal changes are applied (e.g.: only fixing actual errors / adding critical missing info to the documentation)
  • close the PR

dev/README.md Outdated
apply selected AMPs

## Setting up your development environment
## 1. Setting up your development environment
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think this should be a numbered list, a lot of these "steps" are not really steps and are optional depending on the use-case or people may prefer to work in a different way. I think the previous approach with them just being regular paragraphs was more true to the nature of this documentation.

dev/README.md Outdated
@@ -1,70 +1,61 @@
# Development Tomcat Environment

It is possible to use Docker containers to test your code, but it is normally more convenient to simply run the repository webapp (**`alfresco.war`**) and Share webapp (**`share.war`**) in a tomcat instance. Options are also available to apply selected AMPs.
Copy link
Contributor

Choose a reason for hiding this comment

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

A few changes such as this one include very minimal rewording (e.g.: in this case just adding a final . to the sentence) at the cost of losing the formatting that is more convenient to easily scan and maintain the documentation.

Please let's retain the original formatting / try to not go overboard with the length of a single line. Apply a vertical guide line via your IDE to do so if needed, to not break the previous one.

This comment applies to ALL changes in this PR.

dev/README.md Outdated

Aliases ending in `D` provide Maven commands for building local Docker images. The AMPS environment variable will be of
interest, if you wish to build AMPs included in the repo and share projects.
Aliases ending in **`D`** provide Maven commands for building local Docker images. The AMPS environment variable will be of interest, if you wish to build AMPs included in the repo and share projects.
Copy link
Contributor

Choose a reason for hiding this comment

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

No need to make code snippets bold. They have great visibility already, depending on your client's rendering some people might actually find it easier to read non-bold code snippets. (applies to several changes in this PR).

dev/README.md Outdated

The `aliases` file includes a more detailed description.
~~~
**You may also build **`alfresco-community-repository`**, **`alfresco-community-share`** and **`alfresco-community-packaging`** with Docker images at once with **`comD`**.**
Copy link
Contributor

Choose a reason for hiding this comment

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

I think there's no point in explaining this specific alias here, there's many aliases and they should be described appropriately in the aliases file already so that's the source of truth for this kind of information. We don't want to duplicate this so we'd have to maintain it in 2 separate places in case some of the aliases change.

dev/README.md Outdated
done so already), so that your changes are in the community alfresco.war file.
~~~
## 3. Build the Repo project
Build the `alfresco-community-repo` projects with **`comR`**, so that your changes are in the community alfresco.war file.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this rewording here is unnecessary, comR is already mentioned as an alternative in the presented code block that explains how to build the community repo.

dev/README.md Outdated
~~~
# The `entS` alias is the same as the following commands:
## 4. Build the Share project
Build the `alfresco-community-share` project with **`comS`**, so that your changes are in the community share.war file, which also depends on your **`alfresco-community-repo`** project version.
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above, the added note about # The `comS` alias is the same as the following commands: should be sufficient.

dev/README.md Outdated
The simplest way to create these, is to use the `docker-compose.yml` file in the `dev` directory.
~~~
## 5. Docker test environment
The repository code will need to talk to other ACS components, such as a database, message queue and transformers. The simplest way to create these, is to use the **`docker-compose.yml`** file in the **`dev`** directory. Do it with **`envUp`** alias.
Copy link
Contributor

Choose a reason for hiding this comment

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

Unnecessary rewording IMO, the envUp alias is already mentioned just bellow.

@IgorBia
Copy link
Author

IgorBia commented Sep 9, 2024

Hello, thank you for your feedback. I see the errors I've made and things that were not necessarily needed.

I did my best to fix it and even though now it's not that different from original, I've decided to stay with a few changes:

  • changing "entS" to "comS" alias,
  • rewording "alfresco-community-repo project" to "Repo project",
  • bash formatting if needed,
  • adding Helpful links point with references to projects used in the setup process.

Please let me know if everything's OK now.

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