116339ad86
* chore(admin): refactor admin develop/build pipeline chore: remove `webpackChunkName` comments chore: reuse admin tsconfig where possible chore: add .strapi to gitignore chore(admin): pack-up feat(admin): inject commands into strapi from admin for building feat(admin): move watch command to admin chore: keep backward compat API available Update packages/core/admin/_internal/cli/index.ts docs(admin): document the build & develop process and pipeline test(admin): fix StrapiApp tests chore: fix build * Update skipped_tests.yml * test(e2e): fix e2e setup feat: add dependency installation fix: mjs webpack resolution * chore: fix server exports * fix: typescript project type generation * fix: development watch mode * fix: connect to hot middleware – anywhere * Update packages/core/admin/_internal/node/core/monorepo.ts Co-authored-by: Marc Roig <marc12info@gmail.com> * fix(admin): theme toggle type export * chore: fixes * chore: pr amends Co-Authored-By: Ben Irvin <ben@innerdvations.com> --------- Co-authored-by: Marc Roig <marc12info@gmail.com> Co-authored-by: Ben Irvin <ben@innerdvations.com>
getstarted
This is an example app you can run to test your changes quickly.
Requirements
- Docker
- Docker compose
- Node
Installation
By default once you have setup the monorepo you will be able to run the getstarted app with a sqlite DB directly.
If you wish to run the getstarted app with another database you can use the docker-compose.dev.yml file at the root of the directory.
start the databases
Run the following command at the root of the monorepo
docker-compose -f docker-compose.dev.yml up -d
If you need to stop the running databases you can stop them with the following command:
docker-compose -f docker-compose.dev.yml stop
run the getstarted app with a specific database
DB={dbName} yarn develop
The way it works is that the getstarted app has a specific database.js config file that will use the DB environment variable to setup the right database connection. You can look at the code here
Warning
You might have some errors while connecting to the databases.
They might be coming from a conflict between a locally running database instance and the docker instance. To avoid the errors either shutdown your local database instance or change the ports in the ./config/database.js and the docker-compose.dev.yml file.