Running alembic via the container image is problematic about matrix-registration HOT 2 OPEN

https://github.com/ZerataX/matrix-registration/blob/2a36ebb4fa660bbd75600946b592119c497f1fba/docker.nix#L13-L26

I could easily add something to this like

Env = [ "PATH=${pkgs.matrix-registration.alembic}/bin/" ];

and maybe also add a symlink for the ini to /data?
kinda wish i could just set two entrypoints for both alembic and mreg.

Hmm the other nix approach might be to make a wrapper, e.g. I use this:

{
matrix-registration-cli-wrapper = pkgs.stdenv.mkDerivation {
    name = "matrix-registration-cli-wrapper";
    buildInputs = [ pkgs.makeWrapper ];
    buildCommand = ''
      mkdir -p $out/bin
      makeWrapper ${pkgs.matrix-registration}/bin/matrix-registration "$out/bin/matrix-registration" \
        --add-flags "--config-path='${matrix-registration-config}'"
    '';
  };
}

if I put both configured like that on the PATH I could just use a default entrypoint.

then I guess you would have to write out the entire command. as in matrix-registration serve or alembic upgrade head instead of just serve, but overwriting the entrypoint for alembic seems kinda bad?

from matrix-registration.

I'm not sure I understand what the above nix configuration does, but anyway.. writing out the entire command sounds (matrix-registration serve, instead of just serve) sounds good.

from matrix-registration.