Closed (duplicate)
Project:
Provision
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Feb 2011 at 09:33 UTC
Updated:
21 Feb 2011 at 00:37 UTC
I have implemented the UI part, it enables you:
- define a default vhost addition for all sites
- override those settings on a site by site level
- optional token support: being able to replace templates in the vhost entry using tokens
Here is the module: https://github.com/EugenMayer/hosting_vhost_extra
Patch for provision will be here in a second
Comments
Comment #1
eugenmayer commentedComment #2
eugenmayer commentedsee http://drupal.org/node/994210#comment-4100222
Comment #3
anarcat commentedThis looks like the same issue as #1063146: UI: Add an option to add extra vhost settings to sites, please move the discussion there.
Also, I do not understand the reference to #994210: Add support for some common files/subdirs like css/js/ctools/imagecache.
Comment #4
eugenmayer commentedNo comment.....................
If you are here to mark every potential issue as dublicate, just to close issues. Go forward with this. This was the last i opened.
P.S.: The "dupe" you referenced is THIS issue...
moved development into private repo, no need to reopen that one.
Comment #5
anarcat commentedI obviously didn't mean to dupe this to itself. If you would have actually searched the issue queue before opening this ticket (looking for "virtual" or "host"), you would have found (as me) this ticket: #1058918: allow customization of site virtual hosts by the user, which I opened about a week ago, and which I intended to mark this as a dupe of. I screwed up. Sorry.
Yes, I am trying to close issues, as we have 4 pages of them out there. I try my best at reviewing patches that have been given, and would you have been more patient, you would have seen my review for your code, because I opened that other issue this week, upon the request of a co-worker. ie. I need this too. Besides, we all make mistakes and blasting us for everything you consider as such is not constructive.
We have tried to be as patient as we could with this. We have been polite and open. We have tried to process your requests and review your patches to the best of our abilities. So far our efforts have met with snarky comments, threats and abuse. I think this is unfortunate and not an appropriate way to collaborate on an open source project.
That being said, I think it is unfortunate, for everybody involved here, that you would go your own way and develop in a private repository. I hope you will reconsider your decision.
Comment #6
eugenmayer commentedWell i think the things are heated up anyway. I did not "blasting you" for once referencing a wrong dupe and i guess you actually might know this.
Actually this is a series of things happened. It kind of seems when issues are checked, one of the first common things the person is "can i mark this as a dupe". And if there is a slightly chance, do it. Not even try to understand the issue - just close it. Your done, next ticket. Our of sight - out of mind. And this has happened several times and to be hones that isseu is the _first_ on of all those being a real dupe. All the others are simply not understood right or not even tried. And instead of asking, they got marked as dupes.
And all my considerations contributing to the project are currently frozen. Aegir was a lot of work for you guys and actually it has become great in any cases. There are always some bugs or different workflows for the people, but overall its wonderful. Great API ( when you finally undestand the hooks ).. great documentation (coming back to this later).
So i really want(ed) to contribute back, just the common way to say thank you.
But as i seem to got landed on the ignore-level ( or simply the IRC client ) of mig5 and prob. omega8cc and the issue queues are treated like that, my effort and motivation smiply gets killed.
This has a reason and of course also some serious of mistakes of mine. I _never_ considered the documentation to be _that_ good. Why? Iam simply not used to it. Its not even complete on the user-end side and the admin side, its even complete for the dev / API side, even with examples and everything you simply _never_ (close to) see. I did not look into them properly and i might simply asked to many questions which probably got explained / covered there. In addition, i got kind of pissed when nobody answers you anything while you are trying to undestand the system to be able to contribute. Those to things on my hat, and thats why when you got involved, things have been heated up already and surely got not treaded right by me. Next thing on my hat. And i appologize for all those 3 things.
But one thing i think you should consider is: You give the people arround the project the feeling, that everything is covered, no bugs, no misses - everything is perfect. Thats how issues are handled. Thats how "RTFM" is placed. But its _definetly_ not that way. There are issues, there are things not covered.
The second thing is the complexity. Iam pretty involved with drupal development and i consider myself being not a beginner in that field. I have written more then 60 modules and a lot of them are complex enaugh. But still it was not easy to understand aegirs archtecture. Its not the drupal side, thats fine. Its the bridge between aegir hosting and the provistion ( so drush ). That one is pretty hard to get and it opens a lot of stupid questions while you simply did not get when you have what context.
One example is drushrc / drush.inc. While the yourmodule.drush.inc files you place in the module are executed in the drupal-context ( you can call other modules, you have the normal drupal API accessable ), those yourmoule.drush.inc files placed under .drush/ are under the context of drush ( you cant e.g. call module exist). The bridge are drush options, thats how they work together.
Getting all those pieces together takes time _and guidiance_. And you dont guide at all, thats what i really consider your (not you as a person, project lead rather, people deeply involvde ) fault. Because later you expect conributions you want people to help and say thankyou. You dont make that one an easy task at all.
Comment #7
anarcat commentedI think we are getting into a broader discussion that doesn't belong to that issue. You are welcome to state your criticism of the design or project management on the community site. Suggestions of improvements to the design are also welcome as feature requests or tasks in the issue queue.
Comment #8
eugenmayer commentedmoving over to the other issue