【问题标题】:Laravel - Where can I find ~/.bashrcLaravel - 我在哪里可以找到 ~/.bashrc
【发布时间】:2015-04-28 06:47:36
【问题描述】:

我正在关注 Laravel installation guide,但我陷入了以下困境:

确保将 ~/.composer/vendor/bin 目录放在您的 PATH 中,以便您的系统可以找到 laravel 可执行文件。

苦苦挣扎了一个多小时,在这里Laravel installation: How to place the ~/.composer/vendor/bin directory in your PATH?找到了答案

但是,我不确定在哪里可以找到 ~/.bashrc 文件。这是我运行后终端所说的内容

composer global require "laravel/installer=~1.1"

Changed current directory to /Users/meastham/.composer
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files

谁能一步一步解释找到 .bashrc 文件?明明是隐藏文件,所以不是很明显

【问题讨论】:

  • 您使用的是 Windows、Mac OS X 还是 Linux?

标签: laravel


【解决方案1】:

您所遵循的答案是针对 Ubuntu Linux,而不是 MacOS X。在 MacOS X 上,您需要将其添加到 .bash_profile 而不是 .bashrc

只需在/Users/your_username/.bash_profile中的文件末尾添加这一行:

export PATH=~/.composer/vendor/bin:$PATH

This article 解释了如何编辑文件并启动和运行composer

【讨论】:

    【解决方案2】:

    确保你做一个

    ls -a

    这显示隐藏文件。所有以 .是隐藏文件。

    这是一个非常标准的

    # ~/.bashrc: executed by bash(1) for non-login shells.
    # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
    # for examples
    
    # If not running interactively, don't do anything
    [ -z "$PS1" ] && return
    
    # don't put duplicate lines in the history. See bash(1) for more options
    # ... or force ignoredups and ignorespace
    HISTCONTROL=ignoredups:ignorespace
    
    # append to the history file, don't overwrite it
    shopt -s histappend
    
    # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
    HISTSIZE=1000
    HISTFILESIZE=2000
    
    # check the window size after each command and, if necessary,
    # update the values of LINES and COLUMNS.
    shopt -s checkwinsize
    
    # make less more friendly for non-text input files, see lesspipe(1)
    [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
    
    # set variable identifying the chroot you work in (used in the prompt below)
    if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
    fi
    
    # set a fancy prompt (non-color, unless we know we "want" color)
    case "$TERM" in
    xterm-color) color_prompt=yes;;
    esac
    
    # uncomment for a colored prompt, if the terminal has the capability; turned
    # off by default to not distract the user: the focus in a terminal window
    # should be on the output of commands, not on the prompt
    #force_color_prompt=yes
    
    if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it's compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)
    color_prompt=yes
    else
    color_prompt=
    fi
    fi
    
    if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
    else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
    fi
    unset color_prompt force_color_prompt
    
    # If this is an xterm set the title to user@host:dir
    case "$TERM" in
    xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
    *)
    ;;
    esac
    
    # enable color support of ls and also add handy aliases
    if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'
    
    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
    fi
    
    # some more ls aliases
    alias ll='ls -alF'
    alias la='ls -A'
    alias l='ls -CF'
    
    # Add an "alert" alias for long running commands. Use like so:
    # sleep 10; alert
    alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
    
    # Alias definitions.
    # You may want to put all your additions into a separate file like
    # ~/.bash_aliases, instead of adding them here directly.
    # See /usr/share/doc/bash-doc/examples in the bash-doc package.
    
    if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
    fi
    
    # enable programmable completion features (you don't need to enable
    # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
    # sources /etc/bash.bashrc).
    if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
    . /etc/bash_completion
    fi 
    

    【讨论】:

    • 你知道我在哪里可以找到 ~/.bashrc 文件吗?
    • 您好,感谢您的回答,但我应该在哪个目录中运行ls -a。这是我的 .composer 文件/Users/meastham/.composer ./composer.json
    • 您的主目录。使用cd,您将在那里。输入 pwd 以查看我们在您服务器文件系统中的位置。
    • ~ 是您的主目录的简写。
    猜你喜欢
    • 2013-11-08
    • 2014-07-16
    • 2012-05-30
    • 2013-07-13
    • 2012-06-05
    • 2011-04-24
    • 2021-02-02
    • 2016-07-02
    • 1970-01-01
    相关资源
    最近更新 更多