erlware-deprecated / portius Goto Github PK

This might help in debugging cycles.
I'd like to repeatedly build, and faxien publish to portius the same version of an erlang app.
Currently Portius only loads brand new versions.

See discussion:
http://groups.google.com/group/erlware-questions/browse_thread/thread/ae6883512620ec5a
From discussion:

ubercoder View profile
More options Apr 29, 10:18 am

From: ubercoder [email protected]
Date: Thu, 29 Apr 2010 08:18:15 -0700 (PDT)
Local: Thurs, Apr 29 2010 10:18 am
Subject: Can I repeatedly publish the same app+version to portius?
Reply | Reply to author | Forward | Print | Individual message | Show original | Remove | Report this message | Find messages by this author
I'm finding that portius does not process my app if I publish it with
the same version.

I have an app that runs fine on my dev box.
I publish it to portius, then go to another targe machine and install
on there.

The app crashes there, and I'm trying to do some debug iterations.
I tried building on the sourc machine and republishing to portius
("faxien publish").

It seems to go ok, and the newer code and all is in the writable
directory.
However portius never reprocesses it, so the target machine still gets
the older code.

I did a work around by restarting Portius with a new repo every time
(at the moment, only one thing published there).

(1) Is this by design? I'd rather not up the version number on every
debug iteration.

(2) Where is the setting that controls how often Portius checks for
updates?

(3) I am now compiling/testing on the targe machine so I can skip the
package thing, but if I get to the point where I am specifically
testing the publish-install cycle, I'll want to know a more
streamlined way to do this.

Martin Logan View profile
More options Apr 29, 6:58 pm

From: Martin Logan [email protected]
Date: Thu, 29 Apr 2010 18:58:54 -0500
Local: Thurs, Apr 29 2010 6:58 pm
Subject: Re: Can I repeatedly publish the same app+version to portius?
Reply | Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author
Portius expects an updated version every time. This is the desired
behaviour in enterprise. I agree with you that perhaps a setting to
change this would be helpful. This would not be too hard. If you
create a trouble ticket for me I will remember to do it. I may even
have time to look at it tonight. There is no setting to change this.
The way to install your app on other machines during test is without
portius. Faxien can install packages on the local file system as well
as it installs packages from Portius. You can simple scp over
application or release packages and then just point faxien install at
them. You can do something like faxien install-app
_build/development/apps/<app_dir> or faxien install-release
_build/development/tars/<release_tarball>

I hope that helps.

• ...
  oh, and put in a config tuple to control it. I would not want the main
  Erlware repo letting people slip code under version tags.