ectophile alternatives and similar packages
Based on the "ORM and Datamapping" category.
Alternatively, view ectophile alternatives based on common mentions on social networks and blogs.
-
memento
Simple + Powerful interface to the Mnesia Distributed Database 💾 -
paper_trail
Track and record all the changes in your database with Ecto. Revert back to anytime in history. -
ExAudit
Ecto auditing library that transparently tracks changes and can revert them. -
ecto_psql_extras
Ecto PostgreSQL database performance insights. Locks, index usage, buffer cache hit ratios, vacuum stats and more. -
arbor
Ecto elixir adjacency list and tree traversal. Supports Ecto versions 2 and 3. -
sqlitex
An Elixir wrapper around esqlite. Allows access to sqlite3 databases. -
boltun
Transforms notifications from the Postgres LISTEN/NOTIFY mechanism into callback execution -
sql_dust
Easy. Simple. Powerful. Generate (complex) SQL queries using magical Elixir SQL dust.
Static code analysis for 29 languages.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of ectophile or a related project?
Popular Comparisons
README
Ectophile
Ectophile is an extension for Ecto models to instantly support file uploads.
Usage
Ectophile
provides an attachment_fields/2
macro for your model which is used like:
defmodule MyApp.User do
use Ectophile #=> Note that this needs to be used before MyApp.Web so that the callbacks will work
use MyApp.Web, :model
schema "users" do
field :email, :string
attachment_fields :avatar
timestamps
end
...
end
attachment_fields/2
in the above example, defines two different fields which are:
field :avatar, Ectophile.Type
field :avatar_upload, :any, virtual: true
The :avatar
field is where the path to the file in your filesystem and filename is saved. :avatar_upload
is the field we'll use for file uploads.
Keep in mind that you will need to create the necessary migration
to add the Ectophile
fields to your model like so:
defmodule SampleMigration do
use Ecto.Migration
def change do
create table(:users) do
add :email
add :avatar, :jsonb #=> The column we need for Ectophile's custom field
timestamps
end
end
end
Also, set the :otp_app
in your config like:
# config/config.exs
use Mix.Config
config :ectophile, otp_app: :yourapp
In your application's top-level supervisor's start/2
function, add the following to setup the directories where your files will be uploaded:
import Ectophile.Helpers
def start(_type, _args) do
ensure_upload_paths_exist([MyApp.User]) #=> This creates all the required directories for your uploaded files
...
end
After doing the migrations and defining your model's attachment_fields
, you can then add file upload field to your model's form like:
...
<div class="form-group">
<%= label f, :avatar_upload, "Avatar" %>
<%= file_input f, :avatar_upload, class: "form-control" %>
</div>
...
That's it!!! Now every time a user uploads a file and submits a form, that file is stored in a configurable location in your priv/static
directory and a reference to that file is stored in your database.
In your template, you can then do:
<img alt="<%= @user.avatar %>" src="<%= static_path(@conn, Ectophile.Helpers.static_path(avatar)) %>">
Important links
- Documentation - to be published
- License
*Note that all licence references and agreements mentioned in the ectophile README section above
are relevant to that project's source code only.