I am trying to use composer to install a default drupal site. Absolutely basic vanilla.
composer create-project drupal-composer/drupal-project:8.x-dev my_site_name_dir --no-interaction --stability dev
I have had a lot of trouble recently trying to get composer going on my apache web server, both online and in a debian drupal-bitnami environment on my local machine. It just keeps running out of memory, and I have tried various ways of allocating more memory but I am fed up of trying. So
I have several Drupal 8 sites managed with Composer and Git on Shared Hosting.
I recently had problems with Malware creeping in, and I am pretty sure I have tracked it down to the spammers using the phpunit module in the vendor/ folder to get their files onto my servers. I have removed this folder on the production sites, and fingers crossed no more Malware for a while.
My question is this: I would like to minimise the content of the vendor folder as much as possible, so what is the minimum I need for Drupal to run.
I have migrated my live drupal site to local server inorder to work on a new theme. I was able to to migrate and get it running as well. Until I got this exception error while visiting the site. I am not able to trouble shoot this error, kindly help me out. This mainly happened after I was playing with File Permissions in my windows Localhost to set a development environment for a new theme
Additional uncaught exception thrown while handling exception.
I have a local project, that was build in drupal 8 and needs an extra feature.
On that local environment there is machine that produces some files and saves them on the apache server then on a symbolic link that matches one inside the drupal directory.
My nodes have a unique ID and date that are part of the path. Along with a random generater number from the machine.I want to display the files of that directory, directly on the page that displays the data of my content type.
I'm going a deep dive this weekend on JAMStack and in all the reading and videos, one thing is constant. The intro for almost every pro-JAMStack has to spend a paragraph or two bashing "overcomplicated and bloated" CMSes like Drupal (and Wordpress). I can see why people are stoked on JAMStack and the benefits that are potentially available for some sites, but the CMS-bashing seems to be based on some strawman arguments that really go against my experience of CMSes. Does anyone else find the same?