Commits

Rich Manalang [Atlassian]  committed 0532f29

jira->confluence

  • Participants
  • Parent commits 579e09b

Comments (0)

Files changed (2)

-# Atlassian P3 Development Environment
+# Atlassian Connect Confluence Development Environment
 
-This is a set of Vagrant / Puppet provisioning scripts for provisioning a local Atlassian Plugins 3 development environment. To build Plugins 3 Add-ons, you have two choices:
+This is a set of Vagrant / Puppet provisioning scripts for provisioning a local Atlassian Plugins 3 development environment. To build an Atlassian Connect Add-ons, you have two choices:
 
 1. You can build your add-on locally and then register it in an OnDemand instance to test it.
 2. You can build your add-on locally and then register it inside a local version JIRA or Confluence.
 
     vagrant box add base http://files.vagrantup.com/precise32.box
 
-Clone the p3-dev-env-vagrant project by typing at your command line:
+Clone the atlassian-connect-confluence-vagrant project by typing at your command line:
 
-    git clone https://bitbucket.org/rmanalan/p3-dev-env-vagrant.git
-    cd p3-dev-env-vagrant
+    git clone https://bitbucket.org/rmanalan/atlassian-connect-confluence-vagrant.git
+    cd atlassian-connect-confluence-vagrant
 
 Start up and provision automatically all dependencies in the vm:
 
     vagrant up
 
-The last step will provision your local JIRA server and run JIRA. It will take anywhere from 3-5 minutes for your server to be provisioned depending on the speed of your computer. Once it's done, you can access JIRA at:
+The last step will provision your local Confluence server and run Confluence. It will take anywhere from 3-5 minutes for your server to be provisioned depending on the speed of your computer. Once it's done, you can access Confluence at:
 
-    http://localhost:2990/jira (admin/admin)
+    http://localhost:1990/confluence (admin/admin)
 
-### Registering your P3 Add-on
+### Registering your Atlassian Connect Add-on
 
-Once your JIRA server is up and running, you can register your add-on by posting to installer resource:
+Once your Confluence server is up and running, you can register your add-on by posting to installer resource:
 
-    curl -v -u admin -X POST -d url=http://machine_hostname/path/to/your/atlassian-plugin.xml http://localhost:2990/jira/rest/remotable-plugins/latest/installer
+    curl -v -u admin -X POST -d url=http://machine_hostname/path/to/your/atlassian-plugin.xml http://localhost:1990/confluence/rest/remotable-plugins/latest/installer
 
-Notice the URL we're posting to the P3 installer (http://machine_hostname/path/to/your/atlassian-plugin.xml). The `machine_hostname` used here refers to your local machine's hostname. If you're on OSX, this typically will be your `machine_name.local`. You'll need to use the same hostname in your `atlassian-plugin.xml`:
+Notice the URL we're posting to the Atlassian Connect installer (http://machine_hostname/path/to/your/atlassian-plugin.xml). The `machine_hostname` used here refers to your local machine's hostname. If you're on OSX, this typically will be your `machine_name.local`. You'll need to use the same hostname in your `atlassian-plugin.xml`:
 
     <remote-plugin-container key="container" display-url="http://machine_name.local:{port}">
 

File manifests/default.pp

 
 exec {
   "start_jira_in_background":
-  command => "ap3 start jira &",
+  command => "ap3 start confluence &",
   cwd => "/vagrant",
   user => "vagrant",
   path    => "/usr/bin/:/bin/:/home/vagrant/.ap3-sdk/bin/",