david

david

TL;DR: How to ensure that file paths specified in a library when compiled in a macro reflect correct paths at release. /app/_build/prod/lib/library_name/priv/ when compiled vs /app/lib/library_name-version/priv/ when released.

Hi there,
Working on an avatar generation library:
Avatarex - Generate unique, reproducible avatars from hashed strings (*hat tip to @Eiji for help in the rewrite)

I’m a bit confused as to how to ensure that the image asset paths which are being generated at compile time, as part of a using macro, reflect where they’ll actually be at runtime.
So paths that are generated at compile time:
:avatarex |> :code.priv_dir() |> Path.join("sets") |> ...
corresponds to locations that exist during compilation:
/app/_build/prod/lib/avatarex/priv/sets/birdy/body/body_1.png
but are different from the paths that are used at runtime:
/app/lib/avatarex-0.2.0/priv/sets/birdy/body/body_1.png

I do need to be able to File.ls the /app/_build/prod/lib/avatarex/priv/sets/birdy/body/ path at compile time to then generate the list of available images in that directory, but then again at runtime they need to look in /app/lib/....

I thought this may also be related to me not understanding how /app/_build/prod/lib becomes /app/lib upon release.

Thanks,
David

Resources I’ve Reviewed:

Showing Posts 1 to 1

Eiji

Eiji

Oh, I see the point. Since paths are not guaranteed to be the same across different environments and releases we were using :code.priv_dir/1 to get a proper path. However we are doing it at compile time in prod environment and paths were changed in release:thinking:

You should do 2 things:

  1. Rewrite the current compile-time paths to be relative to priv directory. Since contents of priv directory does not changes we can safely call File.ls!/1 on them.
  2. In runtime we need to rewrite relative urls to absolute urls
prod_priv_path = :code.priv_dir(:avatarex)
dir_path = Path.join(~w[sets body])
prod_full_path = Path.join(prod_priv_path, dir_path)
# in struct we store `dir_path`
# for File.ls!/1 we use prod_full_path

def construct(…) do
  release_priv_path = :code.priv_dir(:avatarex)
  images = Enum.map(images, fn {layer, path} -> {layer, Path.join(release_priv_dir, path)} end)
  # …
end

The problem is that images is not the only variable which stores path. You would need to remember when you would update the code.

Let me know if you have some questions.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews