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

Do not create special dir #3

Open
divineforest opened this issue Dec 8, 2014 · 18 comments
Open

Do not create special dir #3

divineforest opened this issue Dec 8, 2014 · 18 comments

Comments

@divineforest
Copy link

I think creating special '.capistrano' dir, which is displayed in first position in editor, is too much noise. Please create .capistrano file instead or use .caprc

@divineforest
Copy link
Author

@leehambley
Copy link
Member

Why not configure your editor to ignore what is by 30 years of computing legacy obviously a hidden directory?

@divineforest
Copy link
Author

Because I do not need it :) Why should I hide .gitignore, .ruby-version, .travis.yml, .rubocop.yml, etc?

@divineforest
Copy link
Author

Why do you use special dir with only one file while other more complicated services use only one hidden file?

@leehambley
Copy link
Member

Because there may in the future be more than one file.

@stereodenis
Copy link

more files for God of Files!

@divineforest
Copy link
Author

Storing one word "false" looks like too much for a separate file. I suggest creating one YAML config file which can handle any number of options. It is a common practice among all ruby related tools and unix general practice as well.

@leehambley
Copy link
Member

We'll be happy to take a PR.

@leehambley
Copy link
Member

It is a common practice among all ruby related tools and unix general practice as well.

Storing configuration in YAML files is not a common UNIX practice.

@divineforest
Copy link
Author

I mean common practice to use one file per tool/service :)

@Fudoshiki
Copy link

+1 for replacing folder on file

@leehambley
Copy link
Member

Feel free to prepare a PR. Please be sure to maintain backwards compatible.

Sent from my Nexus 5.
On 13 Dec 2014 12:01, "Fudoshiki" notifications@github.com wrote:

+1 for replacing folder on file


Reply to this email directly or view it on GitHub
#3 (comment).

@rmonteiro89
Copy link

If it is possible, create the folder .capistrano automatically, because it raises error even if you choose to not send stats

@leehambley
Copy link
Member

Because it raises error even if you choose to not send stats...

What does, specifically, can you share a backtrace?

@rmonteiro89
Copy link

Would you like to enable statistics?  Here is an example message we would
       send:        1|2014-12-19T12:50:58-05:00|2.1.3|x86_64-linux|3.3.3|6df96750
Do you want to enable statistics? (y/N): N
Your preferences have
          been saved.
(Backtrace restricted to imported tasks)
cap aborted!
Errno::ENOENT: No such file or directory @ rb_sysopen - /var/deploy/reporting/.capistrano/metricsTasks: TOP => metrics:collect
(See full trace by running task with --trace)
The deploy has failed with an error: No such file or directory @ rb_sysopen - /var/deploy/reporting/.capistrano/metrics 

@bxt
Copy link

bxt commented Mar 24, 2015

I think one would have to create the folder .capistrano if you want to send statistics and when the directory is not present, capistrano should not complain and just don't send any stats.

@leehambley
Copy link
Member

Just upgrade, this feature was removed from Capistrano weeks ago.
On 24 Mar 2015 7:01 pm, "Bernhard Häussner" notifications@github.com
wrote:

I think one would have to create the folder .capistrano if you want to
send statistics and when the directory is not present, capistrano should
not complain and just don't send any stats.


Reply to this email directly or view it on GitHub
#3 (comment).

@bxt
Copy link

bxt commented Mar 30, 2015

Ugh, I was using the line for Gemfile from capistrano's REAMDE.md wich reads like this on master:

 gem 'capistrano', '~> 3.3.0'

So I got an old version. Thanks! I fixed it by using:

 gem 'capistrano', '~> 3.4.0'

The statistics collection was disabled in capistrano 3.4.0 as mentioned in the changelog.

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

6 participants