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

[docs] Development page is missing a section on how to set up for web dev against non-local server #10048

Closed
chamilad opened this issue Feb 26, 2024 · 0 comments · Fixed by #10049
Labels
enhancement New feature or request

Comments

@chamilad
Copy link
Contributor

Describe what you are trying to accomplish and why in non technical terms
I want to be able to follow the documentation and setup a web dev environment against a non-local backend so that I can customize the web UI.

Describe the solution you'd like
A brief section should be added to the Development/Contributing To The Main Code Base describing how to customize the source code for a non-local server setup. A link already exists, but it points to a non-existent section.

Describe alternatives you've considered
Searched for the vite.config.ts in the documentation.

Additional context
This section points to a section "3a" but it doesn't exist. It looks like the older instructions were removed with #8081 but the new instructions were not added.

@chamilad chamilad added the enhancement New feature or request label Feb 26, 2024
chamilad added a commit to chamilad/frigate that referenced this issue Feb 26, 2024
This adds a section with instructions on editing the source to run the
Web UI against a non-local backend server.

This resolves blakeblackshear#10048
blakeblackshear pushed a commit that referenced this issue Feb 26, 2024
This adds a section with instructions on editing the source to run the
Web UI against a non-local backend server.

This resolves #10048
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant