Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HUGE Confusion with new D P S #260

Closed
szczym opened this issue May 4, 2011 · 4 comments
Closed

HUGE Confusion with new D P S #260

szczym opened this issue May 4, 2011 · 4 comments

Comments

@szczym
Copy link

szczym commented May 4, 2011

i just upgraded to 8.2 and found, that its big problem for users to understand difference between D S P, its adding new layer of complexity on top of existing visioning of platforms via xxx. Current option means that every new user is asking, what are these and when i explain, they don`t understand, because they are not such a professional to use DSP scenario. And 95% will not need that at all in future. For sure its good option for some of users, but for most of (my) users its just a problem.

If would be grait if we could choose in OCTOPUS YES or NO for D S P.

BTW: In my case non of my octopus users (about 8 of them) ever needed to migrate site from one xxx to other xxx because there is no new versions of drupal any more. (as it use to be).

Thank you for your work on baracuda stack !

@omega8cc
Copy link
Owner

omega8cc commented May 7, 2011

There is already a big number of platforms, so adding another Yes/no prompts for those extra dev/stage d6/d7 platforms will only move this WTF to the install process, while the welcome e-mail clearly explains what is the purpose of those extra platforms.

If you think you don't need them because there is no new core version, you may want to re-think the way you use Aegir. It is a good practice to use separate platform for testing modules upgrades and then migrating the site to the updated platform, instead of updating modules in a live platform, so in fact, without extra platforms (now added automatically for you) you are doing something dangerous and against Aegir logic/power, as you always need to upgrade contrib modules from time to time.

@szczym
Copy link
Author

szczym commented May 8, 2011

i agree with you, indeed its a good practice to use DSP scenario, its the highly professional approach. I have asked in name of average drupal webmasters who rarely get into code, just would like to buld a website and clone it from time to time, upgrade once a while. In my opinion for those kind of folks dsp its way too much.

Any way, i will look with optimism for a on/off switch, if you ever implement it.

@JTxt
Copy link

JTxt commented Jun 9, 2011

So in setting up a new site I could pick from:
CiviCRM 4.0.2 P.001
Drupal 7.2 D.001
Drupal 7.2 P.001
Drupal 7.2 S.001

Not knowing that D P S stood for Development, Staging, Production,
I searched for "aegir Drupal 7 platform D S P" and found this, page, but this didn't say what D S P meant clearly, I looked through the setup email and did not find it, so I read the directory names in the platforms folder:

drupal-7.2-stage
drupal-7.2-dev
drupal-7.2-prod

oh yeah.

So perhaps to avoid this confusion they can be renamed to:
CiviCRM 4.0.2 Production.001
Drupal 7.2 Development.001
Drupal 7.2 Production.001
Drupal 7.2 Staging.001
?

Thanks for your helpfulness, sharing and work on this beautiful system.

@omega8cc
Copy link
Owner

omega8cc commented Jun 9, 2011

Good point. This information was missing in the welcome e-mail, and it was only in the upgrade e-mail for some reason, so we added it now: e991746

Note - it is also mentioned/visible in the config section, but only in HEAD so far: https://github.com/omega8cc/nginx-for-drupal/blob/master/OCTOPUS.sh.txt#L80

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants