API Reference Mishka Installer v0.0.3
modules
Modules
This module can hold your dependencies' information in database
At first, we try to get basic information from hex.pm
website; but after releasing some versions of MishkaInstaller,
this API can be useful for managing packages from admin panel.
This module helps you to protect the extension.json file and every action like add or delete or even edit a dependency is happened, it can handle it and create new state.
A module that holds new dependencies' information, and add them into database or validating to implement in runtime
This module is created just for compiling and sourcing, hence if you want to work with Json file and the other compiling dependencies
please see the MishkaInstaller.Installer.DepHandler
module.
## ETS part to optimization state instead of dynamic supervisor and Genserver
public
— Read/Write available to all processes.
protected
— Read available to all processes. Only writable by owner process. This is the default.
private
— Read/Write limited to owner process.
elixir-macros-for-router
elixir macros for router
live(path, live_view, action \ nil, opts \ [])
live "/", TrackappWeb.Live.DepGetter
delete(path, plug, plug_opts, options \ [])
delete("/events/:id", EventController, :action)
forward(path, plug, plug_opts \ [], router_opts \ [])
forward "/admin", SomeLib.AdminDashboard
get(path, plug, plug_opts, options \ [])
get("/events/:id", EventController, :action)
post(path, plug, plug_opts, options \ [])
post("/events/:id", EventController, :action)
put(path, plug, plug_opts, options \ [])
put("/events/:id", EventController, :action)
This event is triggered whenever a user's role is successfully deleted. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_info()
, ip()
, endpoint()
, modifier_user()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user is successfully logged in. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_info()
, ip()
, endpoint()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user is successfully logged out. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_id()
, ip()
, endpoint()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user is successfully added or edited. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_info()
, ip()
, endpoint()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user is successfully added or edited. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_info()
, ip()
, endpoint()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user's role is successfully saved or edited. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_info()
, ip()
, endpoint()
, modifier_user()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user accesses form an authorisation. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_id()
, entries()
, ip()
, endpoint()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user gets an error for authorisation. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes extra()
, ip()
, endpoint()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.
This event is triggered whenever a user is unsuccessfully logged in. if there is any active module in this section on state,
this module sends a request as a Task tool to the developer call function that includes user_info()
, ip()
, endpoint()
.
It should be noted; This process does not interfere with the main operation of the system.
It is just a sender and is active for both side endpoints.