|author||Joey Hess||2017-10-04 14:04:49 -0400|
|committer||Joey Hess||2017-10-04 14:04:49 -0400|
override deploy url with PropellorRepo.hasOriginUrl info
* Made the PropellorRepo.hasOriginUrl property override the repository url that --spin passes to a host. * PropellorRepo.hasOriginUrl type changed to include HasInfo. (API change) This commit was sponsored by Jake Vosloo on Patreon.
Diffstat (limited to 'doc/forum/how_to_boostrap_the_initial_git_repo')
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/forum/how_to_boostrap_the_initial_git_repo/comment_2_84b8e438ef86d2caf4046c6e7950698b._comment b/doc/forum/how_to_boostrap_the_initial_git_repo/comment_2_84b8e438ef86d2caf4046c6e7950698b._comment
new file mode 100644
@@ -0,0 +1,23 @@
+ subject="""comment 2"""
+I don't know what deploy branch trick you're referring to using.
+There is the deploy remote, which I think should do what you want:
+> Additionally, the url of a remote named "deploy", if it exists
+> in your ~/.propellor/ repository, is used as the origin url for
+> the other repositories.
+When you have a deploy remote configured in your local repository,
+the first time you spin a new host, it will clone its /usr/local/propellor
+from the url of the deploy remote. On subsequent spins, it sends the
+url over, and the host's repository's url is updated too.
+The PropellorRepo.hasOriginUrl property doesn't take effect until
+propellor runs with that configuration, which could be a bit of a chicken and
+egg situation. Except hmm, spin could look for that property and use
+repo url instead of the deploy remote's url. Yeah, I've done that now!