Create a fixed environment container (with docker for e.g.) to support starting developers or testers.

[Boldie]

We shall provide an easy to use environment and also a reference environment to support testing and developing. Common used tasks shall be made easy accessible for e.g. using a shell script or similar thing. For e.g. the following stuff shall be possible:

• Load demo data to a database
• Complete setup including easy to use database setup.
• "One-Click" installation and then use for development or testing.
• It is not intended for the usage as a first priority, It can be used but the focus shall be on the development and testing site.

I suggest to make a docker container for this stuff.

[Boldie]

Maybe this is also related to #1041 #1066

[christianlupus]

There is a docker container managed by mhubig. Although I'd like to see it be under official namespace of partkeepr. But this is merely for production and not for development.

One problem is that there needs to be a way to run the setup without calling a set of web sites. This is needed as (at the moment according to my understanding) nobody except for @Drachenkaetzchen knows exactly what happens during setup routine. This needs to be done manually in order to make automated builds and tests possible.

[shafr]

It would be much more convinient to do a docker-compose with PostgreSQL.
And you can export demo site to .sql files (from normal installation) and then import them inside database during intialization.

• What about windows users ?
• What about *pi users ? It would be nice to have embedded database that would not take a lot of space.

[Drachenkaetzchen]

This is needed as (at the moment according to my understanding) nobody except for @Drachenkaetzchen knows exactly what happens during setup routine.

Well, the code is there.

Also, all setup does is to generate the config.php file and wraps symfony commands to setup the environment. See https://wiki.partkeepr.org/wiki/Running_PartKeepr_from_GIT#Updating

[christianlupus]

Well, that is a good source of information. Thank you for the hint @Drachenkaetzchen.

[christianlupus]

Just a small question at @Drachenkaetzchen and @dromer. Where would we put such files? Some repos I have seen use a subfolder, other use a complete own repo for all sort of CI/CD. What would be your preference for partkeepr? Maybe I can do something here but I want to avoid make the work twice.

[dromer]

I agree with @shafr that a simple docker and/or docker-compose file should be enough to get going.

However it is important that there is a volume mounted for any assets and cache that partkeepr needs. Usually everything is self-contained with docker, but in this case a mounted volume is quite necessary.

[dromer]

@christianlupus I think a dockerfile in the root should be fine. Unless it becomes a 'collection' of files then a subdir to keep it a bit neater.