Last post on this thread from me. The final piece of my jigsaw was pointing my newly minted domain at the newly created app instance on gigalixir. I struggled embarrassingly with this. And serves to show that there is a market for PaaS - people like me!

The interface on 1&1 just had me really confused, but my lightbulb, and this’ll make you laugh, was realising www was a subdomain. Now in the last 6-months I’ve lost count of the new tech I’ve had to learn-ish (Elixir, Phoenix, Erlsom, Floki, Brunch, all the front end stuff, it’s a long list). Tackling 1&1 and subdomains - that’s just another very small brick in an otherwise unstable pile of bricks.

The guidance from gigalixir was spot-on but with a small edit just for me. Point a CNAME record for a www subdomain to tls.gigalixir.com.

Happy Christmas everyone.

Needed to do git subtree push --prefix <path/to/dir> gigalixir master

Then needed to add assets_path=apps/islands_interface/assets in phoenix_static_buildpack.config of /island_interface.

Then needed to tweak relative paths for phoenix and phoenix_html. And was able to deploy!

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