Skip to content

Installer paths mixup? #17

Closed
chrisramakers opened this Issue Sep 12, 2011 · 0 comments

2 participants

@chrisramakers

Running the installer here gives issues with the zfs.sh file. You reference the zf.sh file inthere but the paths do not resolve to the correct location. It throws an error ./bin/zfs.sh: line 7: ./zf.sh: No such file or directory

If i'm printing the pwd from the zfs.sh file it resolves to the folder you are executing the install from, not the folder zfs.sh is located in.

$ cd zfskel/scripts/
$ ./install.sh

###################################################
#                                                 #
#        Zend Framework Skeleton Installer        #
#                                                 #
###################################################

- Getting current folder path
- Creating log folders
- Creating cache folder
- Creating temporary folder
- Copying environment file
- Copying config file
- Customizing config file - Enter for default value
   [DATABASE]
      Database name [zfskel]: 
      Database username [root]: 
      Database password: test
      Database host (ip or hostname) [localhost]: 
   [SECURITY]
      Salt for anti-CSRF tokens [162c9557a309ce6841dd9a5035da2def]: 
      Salt for the frontend passwords [790006230e91dd6279a42a814bf5965a]: 
      Salt for the backoffice passwords [8e887cf8e64ab8e7173701a979476567]: 
   [BACKOFFICE CREDENTIALS]
      Username [john.doe]: 
      Password [687b8ded]: 
      Email [29350@mailinator.com]: 
- Modifying config file
- Writing the credentials migration
- Creating log files
- Giving permissions to log and cache folders
- Running the DB migrations
./bin/zfs.sh: line 7: ./zf.sh: No such file or directory

Installation finished

@christophervalles christophervalles pushed a commit that referenced this issue Oct 9, 2011
Christopher Valles close issue #17 and improve fix of issue #12 60c9196
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.