Silent/Automated Setup

Questions
#1

Hello

I would like to be able to install the CMS completely automatically. The demo/blog data should not be installed.

This would allow us to offer the setup directly from the Control Panel.

Can composer create project do this?

Thanks!

#2

Hi @martin.schaible

Yes, this is possible. Try the following:

  1. Run: composer create-project october/october ./octobercms

  2. Navigate to the octobercms directory

  3. Update the .env file with the database configuration

  4. Run php artisan october:migrate

  5. Run php artisan tailor:migrate (optional)

  6. Run php artisan theme:seed demo (optional)

  7. Open http://localhost/admin to create an admin account

You can also combine the three artisan commands with the following (this will seed the demo theme):

php artisan october:install --no-interaction
#3

Hi @daftspunk

Thanks for the answer.

  • If i am in the root folder of the webspace, is the command composer create-project october/october ./ correct? Usualy the CMS goes in the root folder of the webspace.
  • Point 5: Any reason why tailor needs a migration of a brand new installation?
  • Is it possible to use the combined command without seeding the demo data (Blog, etc.)?
#4

Yeah create-project in dot (.) is fine too.

Point 5 is the standard install with the demo theme, etc.

It’s easy enough to remove all that stuff with tailor:prune but the manual process is best if you intentionally don’t want the demo theme/content at all.

There is also october:fresh which deletes the demo theme, we could get it to also call tailor:prune.

However --no-interaction is purely for the happy (non-custom) path.

#5

Why not make it easy and add a switch like eg. -nodemo to not install any demo data?

The same for the UI-based setup: Add a checkbox to disable the installation of any demo stuff.

Why wasting time to remove stuff manually?

Thanks

#6

Because then it would be functionally identical to

php artisan october:migrate
#7

Hi

I don’t understand your answer. What exactly does php artisan october:migrate do?

That doesn’t look like an installation, but rather a migration. What is being migrated and why?

So I’d like to ask again: What needs to be done to ensure that neither demo data, tailoring tools, nor the theme are installed?

thanks