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.

Sign up for GitHub

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

[IGNORE] README: Add cue deps install #53

Merged
merged 1 commit into from
Feb 12, 2025
Merged

[IGNORE] README: Add cue deps install #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,16 +12,17 @@ Most if not all the plugins schemas rely on the [`common` CUE package of the per

The instructions are for the `Table` plugin, replace the name accordingly.

1. Start development server of the plugin: `cd Table; npm run dev`
2. Update the Perses configuration `config.yaml` to use development server for this plugin:
1. Install Cue deps with `go run ./scripts/get-schemas-deps/get-schemas-deps.go`
2. Start development server of the plugin: `cd Table; npm run dev`
3. Update the Perses configuration `config.yaml` to use development server for this plugin:
```yaml
plugin:
dev_environment:
plugins:
- name: Table
disable_schema: false
url: http://localhost:3005
absolute_path: /absolute/path/to/plugin/repository/Table
absolute_path: /absolute/path/to/plugin/repository/table
```
3. Start Perses backend (in `perses` repository): `./scripts/api_backend_dev.sh`
4. Start Perses frontend (in `perses` repository): `cd ui; npm run start`
4. Start Perses backend (in `perses` repository): `./scripts/api_backend_dev.sh`
5. Start Perses frontend (in `perses` repository): `cd ui; npm run start`