From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Sun, 7 Apr 2024 13:41:34 -0500
Subject: new repository

---
 devdocs/vagrant/push%2Fheroku.html | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 devdocs/vagrant/push%2Fheroku.html

(limited to 'devdocs/vagrant/push%2Fheroku.html')

diff --git a/devdocs/vagrant/push%2Fheroku.html b/devdocs/vagrant/push%2Fheroku.html
new file mode 100644
index 00000000..e9468d84
--- /dev/null
+++ b/devdocs/vagrant/push%2Fheroku.html
@@ -0,0 +1,15 @@
+<h1 id="vagrant-push">  Vagrant Push </h1> <h2 id="heroku-strategy">  Heroku Strategy </h2> <p><a href="https://heroku.com/" title="Heroku">Heroku</a> is a public PAAS provider that makes it easy to deploy an application. The Vagrant Push Heroku strategy pushes your application's code to Heroku.</p> <blockquote class="alert alert-warning"> <p><strong>Warning:</strong> The Vagrant Push Heroku strategy requires you have configured your Heroku credentials and created the Heroku application. This documentation will not cover these prerequisites, but you can read more about them in the <a href="https://devcenter.heroku.com">Heroku documentation</a>.</p> </blockquote>
+<p>Only files which are committed to the Git repository will be pushed to Heroku. Additionally, the current working branch is always pushed to the Heroku, even if it is not the "master" branch.</p> <p>The Vagrant Push Heroku strategy supports the following configuration options:</p> <ul> <li>
+<p><a href="#app"><code>app</code></a> - The name of the Heroku application. If the Heroku application does not exist, an exception will be raised. If this value is not specified, the basename of the directory containing the <code>Vagrantfile</code> is assumed to be the name of the Heroku application. Since this value can change between users, it is highly recommended that you add the <code>app</code> setting to your <code>Vagrantfile</code>.</p> </li> <li>
+<p><a href="#dir"><code>dir</code></a> - The base directory containing the Git repository to upload to Heroku. By default this is the same directory as the Vagrantfile, but you can specify this if you have a nested Git directory.</p> </li> <li>
+<p><a href="#remote"><code>remote</code></a> - The name of the Git remote where Heroku is configured. The default value is "heroku".</p> </li> </ul> <h3 id="usage">  Usage </h3> <p>The Vagrant Push Heroku strategy is defined in the <code>Vagrantfile</code> using the <code>heroku</code> key:</p> <div class="highlight"><pre class="highlight ruby" data-language="ruby">config.push.define "heroku" do |push|
+  push.app = "my_application"
+end
+</pre></div>
+<p>And then push the application to Heroku:</p> <div class="highlight"><pre class="highlight shell" data-language="shell">$ vagrant push
+</pre></div><div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
+    <a href="https://www.vagrantup.com/docs/push/heroku.html" class="_attribution-link">https://www.vagrantup.com/docs/push/heroku.html</a>
+  </p>
+</div>
-- 
cgit v1.2.3