ChicagoBoss production deployment

[Spencer Thompson]

Hi 

Myself and a friend are nearing completion of a web app implemented using 'The Boss'.  I'm looking at ways of automating deployment of our app to our production server.  Basically what we want to do is to be able to get a version of our app out of Git, change some macro and language settings, compile the code, then copy the resulting beam files to the ebin directory on the server.  Because of changes that we need to make to various files to make the code production ready, it seems rebar wouldn't work very well for us.  

I've done similar things in Java using ant script which might work but I'd rather not go that way if there is a better Erlang way of doing things.  Is there standard Erlang/ChicagoBoss way of doing this?

Thanks in advance

Spencer

[Evgeny M]

Afaik there's no standard way to do this. Maybe docker?

But what I do is just copy all the project files (beam, .app, /priv/ content and some other) files to a different directory and package it application to .deb and .rpm with https://github.com/jordansissel/fpm/. I have two different config files - one for dev machine, other for the packages, also config file is marked with --config-files attribute so it does not get replaced when package gets installed. All with a single shell script. Then install the package on the server using standard package manager. Installation could be easily automated with a shell script too.

воскресенье, 1 февраля 2015 г., 14:05:18 UTC+3 пользователь Spencer Thompson написал:

[David Welton]

I'd investigate using 'relx' to make an Erlang release, and doing
things like that... that's the "Erlang way". It doesn't cover the
deployment part, but does cover the 'packaging it up' bit, and some
other things as well.

--
David N. Welton

http://www.welton.it/davidw/

http://www.dedasys.com/