https://github.com/elixir-error-tracker/error-tracker
🐛 An Elixir-based built-in error reporting and tracking solution
https://github.com/elixir-error-tracker/error-tracker
elixir elixir-phoenix error-handling error-monitoring error-reporting oban phoenix-framework phoenix-liveview
Last synced: 5 months ago
JSON representation
🐛 An Elixir-based built-in error reporting and tracking solution
- Host: GitHub
- URL: https://github.com/elixir-error-tracker/error-tracker
- Owner: elixir-error-tracker
- License: apache-2.0
- Created: 2024-05-22T15:01:07.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2024-09-13T14:21:33.000Z (8 months ago)
- Last Synced: 2024-09-14T05:15:13.636Z (8 months ago)
- Topics: elixir, elixir-phoenix, error-handling, error-monitoring, error-reporting, oban, phoenix-framework, phoenix-liveview
- Language: Elixir
- Homepage: https://hex.pm/packages/error_tracker
- Size: 3.95 MB
- Stars: 327
- Watchers: 6
- Forks: 13
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# 🐛 ErrorTracker
**An Elixir based built-in error tracking solution.** ErrorTracker captures errors in your application and stores them in the database. It also provides a web dashboard from where you can find, inspect and resolve captured errors.
## Configuration
Take a look at the [Getting Started](/guides/Getting%20Started.md) guide.
## Development
### Initial setup and dependencies
If this is the first time that you set up this project you will to generate the configuration files and adapt their content to your local environment:
```
cp config/dev.example.exs config/dev.exs
cp config/test.example.exs config/test.exs
```
Then, you will need to download the dependencies:
```
mix deps.get
```
### Assets
In order to participate in the development of this project, you may need to know how to compile the assets needed to use the Web UI.
To do so, you need to first make a clean build:
```
mix do assets.install, assets.build
```
That task will build the JS and CSS of the project.
The JS is not expected to change too much because we rely in LiveView, but if
you make any change just execute that command again and you are good to go.
In the case of CSS, as it is automatically generated by Tailwind, you need to
start the watcher when your intention is to modify the classes used.
To do so you can execute this task in a separate terminal:
```
mix assets.watch
```
### Development server
We have a `dev.exs` script that starts a development server.
To run it together with an `IEx` console you can do:
```
iex -S mix dev
```