Closed ehausen closed 5 years ago
For the record "A Drupal installation directory could not be found" was caused by me having too old drush version. I had to force installing drush version 9 with composer
@ehausen can you elaborate on your solution? Is this about the global Drush version on your system? How does one "force install drush version 9 with composer"?
Maintainers, if this is indeed about the global drush version, how can that cause problems given that install.sh uses the local drush: export DRUSH="$DEST_DIR/$COMPOSER_VENDOR_DIR/drush/drush/drush"
which is 9.5.2 in my case?
Sorry, can't really remember at all now. Could maybe find out, if important
Thanks for the quick response. I ended up installing a global Drush 9 (composer require global) and symlinking /usr/local/bin/drush to that drush executable. Then I completely removed the folder where I had tried to install contenta before. After that, it installed smoothly.
That said, I still don't see why a global Drush 9 would be needed. It shouldn't be required I guess.
@ehausen it seems that the sqlite DB URL is invalid: notice the --db-url= \
. If you want to install using sqlite, I recommend you to take a look at https://github.com/contentacms/contenta_jsonapi_project/blob/8.x-2.x/scripts/install-sqlite.sh
It requires to declare: SQLITE_PATH
and SQLITE_DATABASE
in your .env
file.
Please request a re-open if that is not the case.
Thanks for looking into this. So basically you're saying this is not a bug, but a read-the-documentation problem. That's okay.
However, if a .env file must be edited first, shouldn't we conclude that the single-command quick install method described on www.contentacms.org (php -r "readfile('https://raw.githubusercontent.com/contentacms/contenta_jsonapi/8.x-2.x/installer.sh');" > contentacms-quick-installer.sh chmod a+x contentacms-quick-installer.sh ./contentacms-quick-installer.sh
) will never work?
In https://raw.githubusercontent.com/contentacms/contenta_jsonapi/8.x-3.x/installer.sh you'll note:
echo -e "SQLITE_PATH=tmp\nSQLITE_DATABASE=site.sqlite\nSITE_MAIL=admin@localhost\nACCOUNT_MAIL=admin@localhost\nSITE_NAME='Contenta CMS Demo'\nACCOUNT_NAME=admin\nACCOUNT_PASS=$ACCOUNT_PASS" >> $install_path/.env
echo -e "ACCOUNT_PASS=$ACCOUNT_PASS" >> $install_path/.env.local
To account for that.
OK, let's just hope that my problems were a one-time quirk then, not a reproducible problem. Thanks.
Installation went smoothly until
The second time I tried installing it worked differently
Now the sqlite part seemed to go smoothly
I still have problem at the end with the following, but probably not related: