mik-p / docker-wintercms Goto Github PK

• Winter CMS Build: hiltonbanes/wintercms:build.v1.1.2
• PHP Version:
• Database Engine: mariadb:10.4
• Plugins Installed: none

Description:

The Quick Start says:

Login to the backend with the username admin and password admin.

After install it a random password is generated, which is a problem not only because it is not matching the docs but also when using tools like Portainer, where the generated password is not easy to retrieve.

Steps To Reproduce:

Install WinterCMS with the docker-compose file with database support.

Run:

$ docker-compose up -d
$ docker-compose exec web php artisan winter:up

...

Winter.Demo
 - v1.0.1:  First version of Demo
Seeded System 
Seeded Backend 

\Backend\Database\Seeds\DatabaseSeeder reported:
 - The following password has been automatically generated for the "admin" account: Tnq1g8Uj45itsKnYIkVC7p

Go to the backend page.

Try admin:admin as specified on the docs.

It doesn't work.

Spected Behaviour

Use admin:admin as specified on the docs to access the backend.

I have added docker today and getting this error. I have used docker image the latest one.
can anyone point me into right direction?
Thanks in advance.

How to setup sitemap.xml?

https://github.com/wintercms/wn-sitemap-plugin

The Sitemap plugin works out of the box and does not require any direct development to operate.

If I try to install the builder plugin using "composer require winter/wn-builder-plugin", the installation fails with the message:
Problem 1 - Root composer.json requires winter/wn-builder-plugin ^2.0 -> satisfiable by winter/wn-builder-plugin[v2.0.0, v2.0.1, v2.0.2]. - winter/wn-cms-module[v1.0.473, ..., 1.0.x-dev] require composer/installers dev-main as 1.0 -> satisfiable by composer/installers[dev-main]. - Conclusion: don't install composer/installers dev-main (conflict analysis result) - Root composer.json requires winter/wn-cms-module ~1.0.472 -> satisfiable by winter/wn-cms-module[v1.0.473, v1.0.474, 1.0.x-dev].
The same command works fine on a freshly cloned winter 1.1.6.
Perhaps base the container on that version?

Per: https://wintercms.com/releases/v1.2.1
Released: October 20, 2022

I commented out this line to solve the problem:

# git status && git checkout modules/. && \ 

I checked for all releases with WinterCMS v1.2.3:

• php8.1-apache
• php8.1-fpm
• php8.0-apache
• php8.0-fpm