Skip to content

chore: add local dev environment and agent notes - #6143

Open
juliusknorr wants to merge 3 commits into
mainfrom
chore/local-test-setup
Open

juliusknorr wants to merge 3 commits into
mainfrom
chore/local-test-setup

Conversation

@juliusknorr

@juliusknorr juliusknorr commented Oct 2, 2026 •

Copy link
Copy Markdown
Member
  • Target version: main

Summary

Adds a one-command local dev environment and an AGENTS.md describing how to use it to verify changes.

  • npm run dev:server starts Nextcloud (server master) with this checkout mounted on http://localhost:8081 plus Collabora on http://localhost:9980, using @nextcloud/e2e-test-server
  • Static files are served uncached, so npm run watch plus a reload shows changes immediately
  • AGENTS.md lists the checks to run and how to verify frontend changes in a browser (Playwright MCP)

Stacked on #6142, as the dev server targets server master where the new viewer lives.

TODO

Checklist

  • Code is properly formatted
  • Sign-off message is added to all commits
  • Documentation (manuals or wiki) has been updated or is not required

@juliusknorr
juliusknorr force-pushed the fix/6060-nextcloud-viewer-v2 branch 3 times, most recently from 38bb958 to 1738455 Compare October 8, 2026 07:52
Base automatically changed from fix/6060-nextcloud-viewer-v2 to main October 8, 2026 08:54
Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: Julius Knorr <jus@bitgrid.net>
Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: Julius Knorr <jus@bitgrid.net>
Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: Julius Knorr <jus@bitgrid.net>
@juliusknorr
juliusknorr force-pushed the chore/local-test-setup branch from 038d5ad to 6d20a30 Compare October 8, 2026 08:55
@juliusknorr
juliusknorr marked this pull request as ready for review October 8, 2026 10:28
@juliusknorr
juliusknorr requested a review from elzody as a code owner October 8, 2026 10:28
@elzody

elzody commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

Is the use case for this just so that agents can autonomously verify their changes and interact with a local dev setup? Or is there something else, like is this a good prerequisite for eventually migrating tests to Playwright?

@juliusknorr

Copy link
Copy Markdown
Member Author

Both actually. The server setup can be reused for playwright but I use this to ask my agent in combination with playwright-mcp to test and verify changes or to do screenshots automatically.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants