Vulnerabilities | ||||
---|---|---|---|---|
Version | Suggest | Low | Medium | High |
0.7.1 | 0 | 0 | 0 | 0 |
0.7.0 | 0 | 0 | 0 | 0 |
0.6.2 | 0 | 0 | 0 | 0 |
0.6.1 | 0 | 0 | 0 | 0 |
0.6.0-rc.2 | 0 | 0 | 0 | 0 |
0.6.0-rc.1 | 0 | 0 | 0 | 0 |
0.6.0-rc.0 | 0 | 0 | 0 | 0 |
0.5.2 | 0 | 0 | 0 | 0 |
0.5.1-rc.0 | 0 | 0 | 0 | 0 |
0.5.0 | 0 | 0 | 0 | 0 |
0.4.5-rc.0 | 0 | 0 | 0 | 0 |
0.4.4 | 0 | 0 | 0 | 0 |
0.4.2 | 0 | 0 | 0 | 0 |
0.4.0 | 0 | 0 | 0 | 0 |
0.3.0-rc.0 | 0 | 0 | 0 | 0 |
0.2.22 | 0 | 0 | 0 | 0 |
0.2.21 | 0 | 0 | 0 | 0 |
0.2.20 | 0 | 0 | 0 | 0 |
0.2.19 | 0 | 0 | 0 | 0 |
0.2.18 | 0 | 0 | 0 | 0 |
0.2.17 | 0 | 0 | 0 | 0 |
0.2.16-rc.1 | 0 | 0 | 0 | 0 |
0.2.16-rc.0 | 0 | 0 | 0 | 0 |
0.2.15 | 0 | 0 | 0 | 0 |
0.2.14 | 0 | 0 | 0 | 0 |
0.2.13 | 0 | 0 | 0 | 0 |
0.2.12 | 0 | 0 | 0 | 0 |
0.2.11 | 0 | 0 | 0 | 0 |
0.2.10 | 0 | 0 | 0 | 0 |
0.2.9 | 0 | 0 | 0 | 0 |
0.2.8 | 0 | 0 | 0 | 0 |
0.2.7 | 0 | 0 | 0 | 0 |
0.2.6 | 0 | 0 | 0 | 0 |
0.2.5 | 0 | 0 | 0 | 0 |
0.2.4 | 0 | 0 | 0 | 0 |
0.2.3 | 0 | 0 | 0 | 0 |
0.2.1 | 0 | 0 | 0 | 0 |
0.1.6 | 0 | 0 | 0 | 0 |
0.1.5 | 0 | 0 | 0 | 0 |
0.1.3 | 0 | 0 | 0 | 0 |
0.1.2 | 0 | 0 | 0 | 0 |
0.1.0 | 0 | 0 | 0 | 0 |
0.7.1 - this version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform
Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.
MIT - MIT LicenseAn admin UI for Ash resources. Built with Phoenix LiveView.
https://www.youtube.com/watch?v=aFMLz3cpQ8c
First, ensure you've added ash_admin to your mix.exs
file.
{:ash_admin, "~> 0.7.1"}
If you want to use Phoenix 1.7 which has not yet been released, you'll need to use the git branch phoenix-1.7
, i.e
{:ash_admin, github: "ash-project/ash_admin", branch: "phoenix-1.7"}
Ensure your apis are configured in config.exs
config :my_app, ash_apis: [MyApp.Foo, MyApp.Bar]
Add the admin extension to each api you want to show in the admin dashboard, and configure it to show
use Ash.Api,
extensions: [AshAdmin.Api]
admin do
show? true
end
Modify your router to add ash admin at whatever path you'd like to serve it at.
defmodule MyAppWeb.Router do
use Phoenix.Router
import AshAdmin.Router
# AshAdmin requires a Phoenix LiveView `:browser` pipeline
# If you DO NOT have a `:browser` pipeline already, then AshAdmin has a `:browser` pipeline
# Most applications will not need this:
admin_browser_pipeline :browser
scope "/" do
# Pipe it through your browser pipeline
pipe_through [:browser]
ash_admin "/admin"
end
end
Now start your project (usually by running mix phx.server
in a terminal) and visit /admin
in your browser (or whatever path you gave to ash_admin
in your router).
See the documentation in AshAdmin.Resource
and AshAdmin.Api
for information on the available configuration.
To work on ash_admin, you'll want to be able to run the dev app. You'll need to have postgres setup locally, at which point you can do the following:
mix ash_postgres.create
mix migrate
mix migrate_tenants
Then, you can start the app with: mix dev
If you make changes to the resources, you can generate migrations with mix generate_migrations
Ash is made possible by its excellent community!