Do the Composer files by WGET do the same as a Composer project?
Permalink
I used to install C5 by downloading Zips and extracting them manually etc.
Recently I've been installing C5 on SSH servers by doing the 'wget' command by pulling in the alternative from the Download Mirror - this seems to create Composer.json files etc. in the root automatically.
Does this mean that the whole install is now Composer 'controlled' in some way?
I heard it's better to try and install C5 with this sort of a command:
since this makes it easier to update the C5 site for new versions - but: i can't do this because I have Git controlled files in the webfolder already so I cannot do a Composer install because it is a "non empty" folder.
Anyway: I'm just wondering if WGET is a way to get around that last bit.
Recently I've been installing C5 on SSH servers by doing the 'wget' command by pulling in the alternative from the Download Mirror - this seems to create Composer.json files etc. in the root automatically.
Does this mean that the whole install is now Composer 'controlled' in some way?
I heard it's better to try and install C5 with this sort of a command:
composer create-project -n concrete5/composer hello_world
since this makes it easier to update the C5 site for new versions - but: i can't do this because I have Git controlled files in the webfolder already so I cannot do a Composer install because it is a "non empty" folder.
Anyway: I'm just wondering if WGET is a way to get around that last bit.
wget and unzip is essentially the same as unzipping and uploading all the files. php Composer is completely different.
What then do these generated Composer files do after wget?
Ignore them or use them to run a composer validate to check for security reports etc. If you want to actually use them to update the core, then you need to actually install using composer.
