First, thank you for putting up with all of this!

For a long time I was the only contributor to the code and the documentation, and since code is king, I've spent more of my time there.

I'm so glad you've done this analysis, because now we know exactly what to fix. I've made some effort to clean up this stuff, but obviously, not enough.

Let me respond to each item individually, and then we can parse all of this and put together one clean documentation page.

from devshop.

Go To Place

• http://GetDevShop.com is the go to place for now. We hope to keep this page simple and clean, easy to parse for marketing purposes, and easy to navigate from there to the other pages, like the documentation, source code, chat rooms, etc.
• http://docs.devshop.support. This should be the canonical URL for the documentation. This URL works now, it's just that we have the old URL still hanging around (I've updated drupal.org with this new URL). These pages are generated from the source code of the project itself. You are correct in your assumption about the install.md page.
• the Drupal.org project page... I would love to retire this completely except as a placeholder. An image and a link to the other places is all we should have there.

from devshop.

bash install != bash install.sh

Ug, how embarrassing. I've fixed this on getdevshop.com. The command you want is bash install.sh

from devshop.

Hostname

We just recently fixed this by adding "hostname" as an option in the install.sh script. I am updating the documentation to reflect this right now.

from devshop.

install.sh docs

I've cleaned up the comments at the top of install.sh to match the rest of the documentation.

from devshop.

Other gotchas for AWS on Ubuntu include the fact that the user you log into with by default is ubuntu. After getting devshop installed, I ran into additional issues with drush because Amazon's documentation has me ssh in as ubuntu, which isn't in the aegir or www-data groups. Drush commands therefore fail, both on the server and if I have aliases set up from my local box. So I can add ubuntu to those groups, or I can add my ec2 pem file (key) to the aegir "authorized_keys" file and then ssh as aegir (both of these methods worked, by the way), but it still feels like a puzzle.

This is just a part of learning how to operate devshop and aegir. We should add some more information to the end of the install.sh script so users are reminded. I already added a mention about switching to the aegir user for everything to the install docs page: https://devshop.readthedocs.org/en/latest/install/#

All commands should be run as the aegir user. SSH keys uploaded to the front end under "My Account" > "SSH Keys" get saved to /var/aegir/.ssh/authorized_keys... Hmm I need a documentation page on that too!

You should start to SSH in as aegir@server once you have installed devshop.

from devshop.

@jonpugh that's great. The Installing Devshop docs page, in particular, is now much clearer and I think would have been all I needed to feel right at home with my tinkering. D.O. is better too, and it seems like it will be easier to maintain these different channels over time.

The only final two points I'd make are 1) I still think it would be nice to have a link to the install page from the getdevshop.com installation section and 2) do you have a process in place to make sure that the newest release version gets changed in that Installation section? I ended up first installing 0.8.0 last week, then finding out there was a hotfix after running into issues. The fewer places that need to get updated, the better!

Thanks so much for your feedback and attention.

from devshop.

1. I still think it would be nice to have a link to the install page from the getdevshop.com installation section

Totally agree! That page is simply the gh-pages branch. If you want, would you visit the "edit" page and add a link for me? I love pull requests ;) https://github.com/opendevshop/devshop/edit/gh-pages/index.html

2. do you have a process in place to make sure that the newest release version gets changed in that Installation section?

I have it listed in my "release process" instructions, but it is not yet automated. I want to improve this... I think adding placeholders everywhere it mentions a version, and a search/replace in the release.sh helper scripts would be a good thing.

We are working hard to push out a 1.0.0-beta1 today thanks to D6 EOL, and I still have to submit my Drupalcon session applications, and I have to attend DrupalCamp NYC tomorrow, AND I am presenting at the DrupalNYC meetup on wednesday, so that's probably going to have to wait until next week!

from devshop.

Docs improved. We will be more diligent about changing the latest version on release, and will eventually add it to a robo release command.

from devshop.