Gigalixir and .buildpack

The linked documentation says it has to be called .buildpacks, you even quoted that line.

And I have to assume that it has to live in the git-root of your project, but that is an assumption based on how other systems are configured which do see a git repository as their atomic building block, like gitlab-ci, travis, heroku, etc…

@nobbz Norbert, too true. Atom even has an icon for .buildpacks. That’s where I’ll put it and it can only break if it’s not right

Yes that is correct, it should go at the top of your repository.

Hi Jason @axelson
I’ve built my first release using distillery and only ran into a couple of errors the most notable being:

Duplicated modules: 
unicode_util specified in unicode_util_compat and stdlib

Which was fixed with
mix deps.clean --all && mix deps.get

But I’m not understanding a key step with the deploy to gigalixir. I’ve installed the CLI and I’m logged in to my account.
What do I have to do before this works:

git push gigalixir master

The guidance seems to be weighted towards creating the app in gigalixir.
My project is of course working with my own git repo (local and remote).

Any pointers welcomed.

Well, I ran the following command:

gigalixir set_git_remote app_name

And it recognised:

git push gigalixir master

But then it requested a username and password which are apparently not the credentials for the gigalixir CLI / account.

Bit stuck now. Hope this is useful feedback to the folks at gigalixir.

@shotleybuilder did you already login on the command line?

Otherwise maybe it’s your SSH key:

Or maybe your SSH key has a passphrase set on it?

What error are you getting exactly?

Thanks @axelson that’s an idea worth exploring since I’ve not touched ssh. Off to the day job now but I’ll return to this tonight. If that doesn’t help I’ll ask for support from the folks at gigalixir.
Yes, logged into the gigalixir command line and various commands are working against my account.

The solution.

gigalixir create --name app-name

This isn’t explicitly mentioned in the docs so far as I can see. And the thread of the instructions for those with an existing app to deploy branches before app naming gets mentioned.

@jesse has been very helpful. My next problem is the erlsom library, which is breaking my deployment, but that’s another problem for another day!

Edit
Apart from here! Moved — GIGALIXIR 1.4.0 documentation
But my thought process went along the lines of: I have my app, I don’t need to create another … and given the warnings about not being able to change names and things I didn’t want to experiment! However, deleting an app was painless

gigalixir scale -r 0 app-name
gigalixir delete_app app-name

I’m glad you got it sorted out! Jesse is indeed very helpful.

woohoo, it’s deployed! It’s not working (well, some bits are working). My goal this Christmas was a working deploy - well that’s dealt with what I thought would be the hardest part - deploying.

The last piece was switching around my erlsom dependency. The former defaults to ssh which breaks in a container (apparently, what do i know?)

From this:
{:erlsom, git: “git@github.com:willemdj/erlsom.git”}

To this:
{:erlsom, git: “GitHub - willemdj/erlsom: XML parser for Erlang · GitHub”}