Publishing packages with expm is fairly trivial
Defining a package
Every expm package is defined using
Expm.Package record (look at the example)
You can use
expm new [package.exs] command to generate one from a template.
Normally you put this definition into
package.exs. However, if you're intending to publish named versions as well (such as
:head), our suggestion is to put such package definitions into
package.NAME.exs (like here)
Current expm's implementation of security is a little bit funny. There's no need to create an account in order to publish your package.
password options when claiming new package and this username and password combination will be attached to your package on the server. No one without your username and password can update the package.
You can also store your credentials in your user's config ($HOME/.expm.config):
$ expm config:set username johndoe $ expm config:set password myawesomepassword
This way you don't have to specify --username and --password options every time you publish a package.
At this moment it is not possible to delegate the package maintainership to somebody else, but it will not be that way forever.
Although the server will not store your password in plaintext, it would still be advisable to use a separate password from any other system you use. By default, EXPM will connect to expm.co over HTTPS.
The easiest way to publish a package is to use
expm command line utility:
$ expm --username USERNAME --password PASSWORD publish [package.exs]
If it prints out package specification, everything went fine.
Also, if you need to publish it to some other than central repository, you can do so by specifying that repository's URL using --repository/-r option.
You can also publish your package using Expm's API:
repo = Expm.Repository.HTTP.new [url: ...] Expm.Package.publish repo, Expm.Package.read(filename // "package.exs")