Re-locate widget-the-people repo for easier editing

[gregelin]

IJ, Blaine - what do we know about file location of widget-the-people and improving the code?

Right now the WTP repo is in /opt/ on the GM. It would make more sense for the code to be /vagrant where it would be easier to reach and edit.

But I don't know what happens when you edit a node.js app. Do you need to reinstall it by running npm again?

[Atchuu]

See: http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

Opt is used for optional application software packages, such as the WTP. Ideally we would only relocate it if there was a specific reason.

Greg Elin notifications@github.com wrote:

IJ, Blaine - what do we know about file location of widget-the-people
and improving the code?

Right now the WTP repo is in /opt/ on the GM. It would make more
sense for the code to be /vagrant where it would be easier to reach
and edit.

But I don't know what happens when you edit a node.js app. Do you need
to reinstall it by running npm again?

---

Reply to this email directly or view it on GitHub:
#1

[gregelin]

Relocation may not be correct word.

Vagrant by default shares /vagrant dir with the directory in which Vagrant machine installed. I find it nice to be able to open up the app code in Sublime on my Mac and use all my Mac tools on the code. It might be we just want to link the GM/opt dir the Host//opt.

Greg

Sent from my iPhone

On May 28, 2013, at 10:30 AM, Blaine notifications@github.com wrote:

See: http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

Opt is used for optional application software packages, such as the WTP. Ideally we would only relocate it if there was a specific reason.

Greg Elin notifications@github.com wrote:

IJ, Blaine - what do we know about file location of widget-the-people
and improving the code?

Right now the WTP repo is in /opt/ on the GM. It would make more
sense for the code to be /vagrant where it would be easier to reach
and edit.

But I don't know what happens when you edit a node.js app. Do you need
to reinstall it by running npm again?

---

Reply to this email directly or view it on GitHub:
#1
—
Reply to this email directly or view it on GitHub.

[IkjaePark]

I think as far as the repo location goes, we can change it to /vagrant
folder and shouldn't be an issue. With the current setup (without doing a
vagrant destroy and up with the updated manifest file), you should be able
to just move the directory to /vagrant and do a node app.js (all of the
packages that are required by the app get installed within the directory).

I will test it later today.

IJ

On Tue, May 28, 2013 at 2:22 PM, Greg Elin notifications@github.com wrote:

Relocation may not be correct word.

Vagrant by default shares /vagrant dir with the directory in which Vagrant
machine installed. I find it nice to be able to open up the app code in
Sublime on my Mac and use all my Mac tools on the code. It might be we just
want to link the GM/opt dir the Host//opt.

Greg

Sent from my iPhone

On May 28, 2013, at 10:30 AM, Blaine notifications@github.com wrote:

See: http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

Opt is used for optional application software packages, such as the WTP.
Ideally we would only relocate it if there was a specific reason.

Greg Elin notifications@github.com wrote:

IJ, Blaine - what do we know about file location of widget-the-people
and improving the code?

Right now the WTP repo is in /opt/ on the GM. It would make more
sense for the code to be /vagrant where it would be easier to reach
and edit.

But I don't know what happens when you edit a node.js app. Do you need
to reinstall it by running npm again?

---

Reply to this email directly or view it on GitHub:
#1
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-18569930
.

[jlank]

Do we want /vagrant to be where our application code lives or the runtimes/binary executable files for the vm?

Sent from my iPhone

On May 28, 2013, at 2:29 PM, Chunhamujuk notifications@github.com wrote:

I think as far as the repo location goes, we can change it to /vagrant
folder and shouldn't be an issue. With the current setup (without doing a
vagrant destroy and up with the updated manifest file), you should be able
to just move the directory to /vagrant and do a node app.js (all of the
packages that are required by the app get installed within the directory).

I will test it later today.

IJ

On Tue, May 28, 2013 at 2:22 PM, Greg Elin notifications@github.com wrote:

Relocation may not be correct word.

Vagrant by default shares /vagrant dir with the directory in which Vagrant
machine installed. I find it nice to be able to open up the app code in
Sublime on my Mac and use all my Mac tools on the code. It might be we just
want to link the GM/opt dir the Host//opt.

Greg

Sent from my iPhone

On May 28, 2013, at 10:30 AM, Blaine notifications@github.com wrote:

See: http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

Opt is used for optional application software packages, such as the WTP.
Ideally we would only relocate it if there was a specific reason.

Greg Elin notifications@github.com wrote:

IJ, Blaine - what do we know about file location of widget-the-people
and improving the code?

Right now the WTP repo is in /opt/ on the GM. It would make more
sense for the code to be /vagrant where it would be easier to reach
and edit.

But I don't know what happens when you edit a node.js app. Do you need
to reinstall it by running npm again?

---

Reply to this email directly or view it on GitHub:
#1
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-18569930
.

—
Reply to this email directly or view it on GitHub.

[gregelin]

Well, I think we should look at what others are doing. So I do not know what is best.

My current thinking:

• on apps I am building, I have a folder structure like this
  /
  apps
  docs
  data
  envs
  Vagrantfile
  .git

envs is for environments and is subdivided with /v1, /v2, etc. the manifests and chef files are follow this pattern: envs/v1/Chef/...

It is an app-centric view with computing environment springing out of app sort of speak.

• there may not be a correct answer. Some machines may have very specific requirements.

Greg

Sent from my iPhone

On May 28, 2013, at 3:25 PM, John Lancaster notifications@github.com wrote:

Do we want /vagrant to be where our application code lives or the runtimes/binary executable files for the vm?

Sent from my iPhone

On May 28, 2013, at 2:29 PM, Chunhamujuk notifications@github.com wrote:

I think as far as the repo location goes, we can change it to /vagrant
folder and shouldn't be an issue. With the current setup (without doing a
vagrant destroy and up with the updated manifest file), you should be able
to just move the directory to /vagrant and do a node app.js (all of the
packages that are required by the app get installed within the directory).

I will test it later today.

IJ

On Tue, May 28, 2013 at 2:22 PM, Greg Elin notifications@github.com wrote:

Relocation may not be correct word.

Vagrant by default shares /vagrant dir with the directory in which Vagrant
machine installed. I find it nice to be able to open up the app code in
Sublime on my Mac and use all my Mac tools on the code. It might be we just
want to link the GM/opt dir the Host//opt.

Greg

Sent from my iPhone

On May 28, 2013, at 10:30 AM, Blaine notifications@github.com wrote:

See: http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

Opt is used for optional application software packages, such as the WTP.
Ideally we would only relocate it if there was a specific reason.

Greg Elin notifications@github.com wrote:

IJ, Blaine - what do we know about file location of widget-the-people
and improving the code?

Right now the WTP repo is in /opt/ on the GM. It would make more
sense for the code to be /vagrant where it would be easier to reach
and edit.

But I don't know what happens when you edit a node.js app. Do you need
to reinstall it by running npm again?

---

Reply to this email directly or view it on GitHub:
#1
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-18569930
.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

[gregelin]

Btw, I was able to get widget-the-people launching via build from source and rpm. Check basecamp notes. Rpm was 4.7 min vs 17 min on MacBook Air.

I would think the yum branch of rpm and master branch could be merged and either have two manifests tha you choose in vagrant file by commenting out on or other, maybe there is a default rpm build but you can pass a parameter through vagrant to force build from source?

Greg

Sent from my iPhone

On May 28, 2013, at 2:29 PM, Chunhamujuk notifications@github.com wrote:

I think as far as the repo location goes, we can change it to /vagrant
folder and shouldn't be an issue. With the current setup (without doing a
vagrant destroy and up with the updated manifest file), you should be able
to just move the directory to /vagrant and do a node app.js (all of the
packages that are required by the app get installed within the directory).

I will test it later today.

IJ

On Tue, May 28, 2013 at 2:22 PM, Greg Elin notifications@github.com wrote:

Relocation may not be correct word.

Vagrant by default shares /vagrant dir with the directory in which Vagrant
machine installed. I find it nice to be able to open up the app code in
Sublime on my Mac and use all my Mac tools on the code. It might be we just
want to link the GM/opt dir the Host//opt.

Greg

Sent from my iPhone

On May 28, 2013, at 10:30 AM, Blaine notifications@github.com wrote:

See: http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

Opt is used for optional application software packages, such as the WTP.
Ideally we would only relocate it if there was a specific reason.

Greg Elin notifications@github.com wrote:

IJ, Blaine - what do we know about file location of widget-the-people
and improving the code?

Right now the WTP repo is in /opt/ on the GM. It would make more
sense for the code to be /vagrant where it would be easier to reach
and edit.

But I don't know what happens when you edit a node.js app. Do you need
to reinstall it by running npm again?

---

Reply to this email directly or view it on GitHub:
#1
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-18569930
.

—
Reply to this email directly or view it on GitHub.