Mustache conflict at release build - erlang

I use wooga's fork of mustache.erl (https://github.com/wooga/mustache.erl) in my project. And when I try to create release I get an error because rebar uses this mustache.beam file instead of a file included in its source.
What should I do to resolve this conflict?

The reason is not in rebar but is that some app in release tool search path contains the mustache.erl file as you release does.
Usually rel.config file contains {lib_dirs, ["../.."]} that force release tool search libs (apps) up your release directory. See example below. To fix it, move your release directory dipper (for example -> you_release/you_release) or move app that contains the same file (mustache.erl) to other place.
├── your_release_directory
│   ├── deps
│   │   └── mustache
│   │   ├── ebin
│   │   │   ├── mustache.app
│   │   │   └── mustache.beam
│   │   └── src
│   │   ├── mustache.app.src
│   │   └── mustache.erl
│   ├── ebin
│   │   └── mustache.beam
├── rebar (or any other app contains mustache.erl)
│   ├── ebin
│   │   └── mustache.beam
│   ├── src
│   │   └── mustache.erl

Related

Remove some class file from all jars packaged in tar(each tar is a layer of a docker image)

OK so I know how to remove class files from all the jars under a dir. But, now I have different layer from a docker image, each layer is a tar file, and in the tar file there are the jar files.
Can I remove the class files from the jar files, packaged in tar files?
$ tree -L 3
.
├── 29e0fb8afe376cb02219c977cba1c9a80cca895f7f17b72c356f3e25a63337b9
│   ├── json
│   ├── layer.tar
│   └── VERSION
├── 3b75d6634da4d4f4932d2affeabb7454dc51ba160c3833b386c34e328da8f0ba
│   ├── amq # <<<<< this layer is extracted already, and you can see all the jars here. Other layers are not
│   │   ├── activemq-all-5.11.0.redhat-630495.jar
│   │   ├── bin
│   │   ├── conf
│   │   ├── data
│   │   ├── docs
│   │   ├── examples
│   │   ├── lib
│   │   ├── LICENSE
│   │   ├── NOTICE
│   │   ├── README.txt
│   │   ├── webapps
│   │   └── webapps-demo
│   ├── json
│   ├── layer.tar
│   ├── temp
│   └── VERSION
├── c1fa0e994b2d29f60fd2a6caecbe1ac3f987d001903523d60e532b6e08b094f0
│   ├── json
│   ├── layer.tar
│   └── VERSION
├── c8c84a6c1be5bdfc8caafd23082fd725e84f1c9cddb98fd56cad3a62544b2a3c.json
├── ef5088f89fbac64d2d5982ba14492227f60db1221f6bfd6290c6364a2a95a7e3
│   ├── json
│   ├── layer.tar
│   └── VERSION
├── manifest.json
├── repositories
└── script.sh # <<<<< the script is here
So you ask me why?
Well, did you hear people talking about log4j recently? :) I am doing this right now: log4j vulnerability check: how to quickly detect if log4j is used, in mavevn/in an image? "mvn dependency:tree" does not give a full picture
If someone can tell me how to remove these classes from jib maven plugin, that's better. They are from a base image and I doubt we could do that, though.

docker-compose up with multiple yml confs does not start off

This is the tree structure of my project:
.
├── backend-codebase
│   ├── app.js
│   ├── bin
│   │   └── www
│   ├── config.js
│   ├── db
│   │   ├── index.js
│   │   ├── repos
│   │   │   └── todos.js
│   │   └── sql
│   │   ├── index.js
│   │   └── todos
│   ├── dev
│   │   └── postgres
│   ├── index.js
│   ├── package.json
│   ├── public
│   │   ├── images
│   │   ├── javascripts
│   │   └── stylesheets
│   │   └── style.css
│   ├── routes
│   │   ├── api.js
│   │   ├── index.js
│   │   └── users.js
│   ├── scripts
│   │   ├── applyFixtures.js
│   │   ├── dev_entrypoint.sh
│   │   ├── fixtures.json
│   │   └── psql_dump.sql
│   ├── views
│   │   ├── api.ejs
│   │   ├── db.ejs
│   └── yarn.lock
├── dev
│   ├── Dockerfile-node
│   ├── Dockerfile-postgres
│   ├── development.sh
│   ├── docker-compose-common.yml
│   ├── docker-compose-dev.yml
│   └── postgres
│   ├── 12-12-2016_16_58_59.dump
...
I use docker-compose in order to create three containers and orcherstrate everything:
- a node server
- a postgres DB
- a data container for the DB
plus, I created two (and a third one is missing) yaml files under /dev/docker-compose-*.yml. docker-compose-dev extends the common one and should build the images as well as run all the images.
In order to start off everything I tried to launch the following:
$ docker-compose up --file dev/docker-compose-common.yml --file dev/docker-compose-dev.yml
But what I get is this output:
Builds, (re)creates, starts, and attaches to containers for a service.
Unless they are already running, this command also starts any linked services.
The `docker-compose up` command aggregates the output of each container. When
the command exits, all cont
I really don't understand what I'm doing wrong
Silly, silly me.
It was simply the order between the arguments and the command upside-down.
Plus, I can remove the first --file argument, since it is referenced by using the extends yaml key.
docker-compose -f dev/docker-compose-dev.yml up

How can I import my old tweak written and compiled on iOS device with Theos into Xcode?

I have some old tweak which doesn't work on iOS 8.4 and I wanted to debug it and possibly fix it. I am in no way good with writing tweaks, this was something I did for a friend and me and people used it since I published it on BigBoss.
Anyway at the time, I did not have OS X device and I written everything on iPhone using vi over ssh and then I compiled it on iPhone with Theos.
Now I have OS X device and I wanted to import this into Xcode. Is this even possible? If so how can I do this in most easiest way? I already have iOSOpenDev. Here is folder tree:
├── Makefile
├── NoIconLabels.plist
├── Tweak.xm
├── Tweak.xm.bak
├── _
│   ├── DEBIAN
│   │   └── control
│   └── Library
│   ├── MobileSubstrate
│   │   └── DynamicLibraries
│   │   ├── NoIconLabels.dylib
│   │   └── NoIconLabels.plist
│   ├── PreferenceBundles
│   │   └── NoIconLabels.bundle
│   │   ├── Info.plist
│   │   ├── NoIconLabels
│   │   └── NoIconLabels.plist
│   └── PreferenceLoader
│   └── Preferences
│   └── NoIconLabels.plist
├── control
├── me.itn.noiconlabels_0.1-2_iphoneos-arm.deb
├── me.itn.noiconlabels_0.1-3_iphoneos-arm.deb
├── me.itn.noiconlabels_0.1-4_iphoneos-arm.deb
└── noiconlabels
├── Makefile
├── NoIconLabels.mm
├── Resources
│   ├── Info.plist
│   └── NoIconLabels.plist
├── entry.plist
└── obj
├── NoIconLabels.bundle
│   ├── Info.plist
│   ├── NoIconLabels
│   └── NoIconLabels.plist
├── NoIconLabels.mm.46c9b2c9.o
└── NoIconLabels.mm.ea49af4e.o
Thanks!

Error when start erlang application (relx) release

When I try to start erlang release prepared by relx it crashes with reason:
{"init terminating in do_boot",{badarg,[{erl_prim_loader,check_file_result,3,[]},{init,get_boot,1,[]},{init,get_boot,2,[]},{init,do_boot,3,[]}]}}
Directory listing:
├── bin
├── lib
│   ├── asn1-2.0.2
│   │   ├── ebin
│   │   ├── priv
│   │   └── src
│   ├── bear-0.8.1
│   │   ├── ebin
│   │   └── src
│   ├── cache-1.0.0
│   │   ├── ebin
│   │   ├── priv
│   │   └── src
│   ├── cberl-1
│   │   ├── c_src
│   │   ├── ebin
│   │   ├── include
│   │   ├── priv
│   │   └── src
│   ├── compiler-4.9.2
│   │   ├── ebin
│   │   └── src
│   ├── cowboy-0.8.6
│   │   ├── ebin
│   │   └── src
....................
│   ├── crypto-3.0
│   │   ├── ebin
│   │   ├── priv
│   │   │   └── lib
│   │   └── src
└── releases
└── 0.5.2
All libraries on it's own places.
I tried to start application with the command erl -env ERL_LIBS ../libs -erlconto and it successfully started.
It seems, that problem in boot file, but i don't know how to approach this problem.
Any tips or way to solve, please.
Tnx!
I added
{extended_start_script, true}.
to relx.conf an application now work!
Tnx.
This usually happens when OTP application's .app file is missing a required dependency. relx uses the contents of .app to resolve dependencies to go into the release.
Make sure all of your release applications include, at least, kernel and stdlib in the applications tuple in .app.
Here is an example .app file listing kernel, stdlib, and elk as dependencies:
{application, prop, [
{description, "Prop Template Generator"},
{vsn, "0.0.1"},
{registered, []},
{applications, [kernel, stdlib, elk]},
{modules, [prop, prop_otp, prop_generator]},
{env, []}
]}.

pub serve Transformer library "package:observe/transformer.dart" not found

When run pub serve on Mac, it could not find transformer.dart:
Transformer library "package:observe/transformer.dart" not found
I'm using OSX 10.9, DartEditor 30798.
pub build works fine.
I searched and saw pub build fails if proxy is define. But I'm connecting to network directory without proxy.
Here is the observe package under packages directory, transformer.dart is there:
observe
├── html.dart
├── observe.dart
├── src
│   ├── bind_property.dart
│   ├── change_notifier.dart
│   ├── change_record.dart
│   ├── compound_path_observer.dart
│   ├── dirty_check.dart
│   ├── list_diff.dart
│   ├── list_path_observer.dart
│   ├── metadata.dart
│   ├── microtask.dart
│   ├── observable.dart
│   ├── observable_box.dart
│   ├── observable_list.dart
│   ├── observable_map.dart
│   ├── path_observer.dart
│   └── to_observable.dart
├── transform.dart
└── transformer.dart
I had such problem in the renamed polymer project. After I made new polymer project and copy all logic in created files. The problem was solved.

Resources