Skip to content

Conversation

@Jurj-Bogdan
Copy link
Member

Added a new "security" section to the admin documentation.

I was unsure how much detail to add - should i add recommended config values, code examples?

Closes #16

Signed-off-by: Jurj-Bogdan <bogdanjurj11@gmail.com>
Signed-off-by: Jurj-Bogdan <bogdanjurj11@gmail.com>
@Jurj-Bogdan Jurj-Bogdan requested a review from bidi47 September 30, 2025 09:28
@Jurj-Bogdan Jurj-Bogdan added the documentation Improvements or additions to documentation label Sep 30, 2025
mkdocs.yml Outdated
- "Inject Dependencies": v6/how-to/dependency-injection.md
- "Set Up CSRF": v6/how-to/csrf.md
- Security:
- "Security Observations": v6/security/security.md
Copy link
Member

Choose a reason for hiding this comment

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

Security Observations
can be

Security

Copy link
Member

Choose a reason for hiding this comment

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

let's better use the term
"Basic Security"
as it is only a minimum, a starting point, a mandatory stuff

Copy link
Member

Choose a reason for hiding this comment

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

  • "Security Observations": v6/security/security.md
    will be
  • "Basic Security Observations": v6/security/basic-security.md

composer development-status
```

- `Admin` ships with a `laminas/laminas-ci` integration, consider keeping it in your custom applications to ensure code quality.
Copy link
Member

Choose a reason for hiding this comment

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

add a link to lamians-ci , or to the article relatd to it from getlaminas.org

Copy link
Member

Choose a reason for hiding this comment

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

There is no such repo laminas/laminas-ci.

We should probably add the reference to https://github.com/laminas/laminas-continuous-integration because that is the package used in our repo: https://github.com/dotkernel/admin/blob/6.0/.github/workflows/continuous-integration.yml#L11

Signed-off-by: Jurj-Bogdan <bogdanjurj11@gmail.com>
composer development-status
```

- `Admin` ships with a [Laminas Continuous Integration GitHub Action](https://github.com/laminas/laminas-continuous-integration-action), consider keeping it in your custom applications to ensure code quality.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- `Admin` ships with a [Laminas Continuous Integration GitHub Action](https://github.com/laminas/laminas-continuous-integration-action), consider keeping it in your custom applications to ensure code quality.
- `Admin` ships with a [Laminas Continuous Integration](https://github.com/laminas/laminas-continuous-integration-action) GitHub action, consider keeping it in your custom applications to ensure code quality.

It's enough calling the link "Laminas Continuous Integration" and makes more sense leaving "GitHub action" after it.

Copy link
Member

@alexmerlin alexmerlin Oct 3, 2025

Choose a reason for hiding this comment

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

Maybe you should also mention that keeping the GHA in their repo makes sense only if the repo is public.
IIRC, (unless adding some token) the action will not run on private repos - @arhimede please confirm.

Copy link
Member

Choose a reason for hiding this comment

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

Maybe you should also mention that keeping the GHA in their repo makes sense only if the repo is public. IIRC, (unless adding some token) the action will not run on private repos - @arhimede please confirm.

confirmed, is not working on private repos

Signed-off-by: Jurj-Bogdan <bogdanjurj11@gmail.com>
Signed-off-by: Jurj-Bogdan <bogdanjurj11@gmail.com>
Signed-off-by: Jurj-Bogdan <bogdanjurj11@gmail.com>
@arhimede arhimede merged commit b774f0c into main Oct 6, 2025
8 checks passed
@alexmerlin alexmerlin deleted the issue16 branch October 6, 2025 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

security section

4 participants