|
1 | | -# Mezzio Skeleton and Installer |
| 1 | +# Queue |
2 | 2 |
|
3 | | -[](https://github.com/mezzio/mezzio-skeleton/actions/workflows/continuous-integration.yml) |
4 | | - |
5 | | -> ## 🇷🇺 Русским гражданам |
6 | | -> |
7 | | -> Мы, участники Laminas, родились и живем в разных странах. У многих из нас есть друзья, родственники и коллеги как в России, так и в Украине. Некоторые из нас родились в России. Некоторые из нас живут в России. У некоторых бабушки и дедушки сражались с фашистами во Второй мировой войне. Здесь никто не поддерживает фашизм. |
8 | | -> |
9 | | -> У одного из нас есть украинская родственница, которая спаслась из дома вместе с сыном. Поезд задержался из-за бомбежки на дороге впереди. У нас есть друзья, которые прячутся в бомбоубежищах. Мы с тревогой ждем весточки от них после воздушных налетов, которые беспорядочно наносят удары и попадают по больницам, школам, детским садам и домам. Мы не берем это из каких-либо СМИ. Мы наблюдаем это напрямую. |
10 | | -> |
11 | | -> Вы доверяете нам достаточно, чтоб использовать наши программы, и мы просим вас довериться нам вновь. Мы нуждаемся в помощи. Выходите и протестуйте против этой бесполезной войны. Остановите кровопролитие. Скажите "Нет войне!" |
12 | | -> |
13 | | -> ## 🇺🇸 To Citizens of Russia |
14 | | -> |
15 | | -> We at Laminas come from all over the world. Many of us have friends, family and colleagues in both Russia and Ukraine. Some of us were born in Russia. Some of us currently live in Russia. Some have grandparents who fought Nazis in World War II. Nobody here supports fascism. |
16 | | -> |
17 | | -> One team member has a Ukrainian relative who fled her home with her son. The train was delayed due to bombing on the road ahead. We have friends who are hiding in bomb shelters. We anxiously follow up on them after the air raids, which indiscriminately fire at hospitals, schools, kindergartens and houses. We're not taking this from any media. These are our actual experiences. |
18 | | -> |
19 | | -> You trust us enough to use our software. We ask that you trust us to say the truth on this. We need your help. Go out and protest this unnecessary war. Stop the bloodshed. Say "stop the war!" |
20 | | -
|
21 | | -*Begin developing PSR-15 middleware applications in seconds!* |
22 | | - |
23 | | -[mezzio](https://github.com/mezzio/mezzio) builds on |
24 | | -[laminas-stratigility](https://github.com/laminas/laminas-stratigility) to |
25 | | -provide a minimalist PSR-15 middleware framework for PHP with routing, DI |
26 | | -container, optional templating, and optional error handling capabilities. |
27 | | - |
28 | | -This installer will setup a skeleton application based on mezzio by |
29 | | -choosing optional packages based on user input as demonstrated in the following |
30 | | -screenshot: |
31 | | - |
32 | | - |
33 | | - |
34 | | -The user selected packages are saved into `composer.json` so that everyone else |
35 | | -working on the project have the same packages installed. Configuration files and |
36 | | -templates are prepared for first use. The installer command is removed from |
37 | | -`composer.json` after setup succeeded, and all installer related files are |
38 | | -removed. |
39 | | - |
40 | | -## Getting Started |
41 | | - |
42 | | -Start your new Mezzio project with composer: |
43 | | - |
44 | | -```bash |
45 | | -$ composer create-project mezzio/mezzio-skeleton <project-path> |
46 | | -``` |
47 | | - |
48 | | -After choosing and installing the packages you want, go to the |
49 | | -`<project-path>` and start PHP's built-in web server to verify installation: |
50 | | - |
51 | | -```bash |
52 | | -$ composer serve |
53 | | -``` |
54 | | - |
55 | | -You can then browse to http://localhost:8080. |
56 | | - |
57 | | -## Installing alternative packages |
58 | | - |
59 | | -There is a feature to install alternative packages: Instead of entering one of |
60 | | -the selection **you can actually type the package name and version**. |
61 | | - |
62 | | -> ```text |
63 | | -> Which template engine do you want to use? |
64 | | -> [1] Plates |
65 | | -> [2] Twig |
66 | | -> [3] zend-view installs zend-servicemanager |
67 | | -> [n] None of the above |
68 | | -> Make your selection or type a composer package name and version (n): infw/pug:0.1 |
69 | | -> - Searching for infw/pug:0.1 |
70 | | -> - Adding package infw/pug (0.1) |
71 | | -> ``` |
72 | | -
|
73 | | -That feature allows you to install any alternative package you want. It has its limitations though: |
74 | | -
|
75 | | -* The alternative package must follow this format `namespace/package:1.0`. It needs the correct version. |
76 | | -* Templates are not copied, but the ConfigProvider can be configured in such way that it uses the |
77 | | - default templates directly from the package itself. |
78 | | -* This doesn't work for containers as the container.php file needs to be copied. |
79 | | -
|
80 | | -## Troubleshooting |
| 3 | +> [!IMPORTANT] |
| 4 | +> Dotkernel component used to queue tasks to be processed asynchronously based on [netglue/laminas-messenger](https://github.com/netglue/laminas-messenger) |
81 | 5 |
|
82 | | -If the installer fails during the ``composer create-project`` phase, please go |
83 | | -through the following list before opening a new issue. Most issues we have seen |
84 | | -so far can be solved by `self-update` and `clear-cache`. |
| 6 | +## Badges |
85 | 7 |
|
86 | | -1. Be sure to work with the latest version of composer by running `composer self-update`. |
87 | | -2. Try clearing Composer's cache by running `composer clear-cache`. |
| 8 | + |
| 9 | + |
88 | 10 |
|
89 | | -If neither of the above help, you might face more serious issues: |
| 11 | +[](https://github.com/dotkernel/queue/issues) |
| 12 | +[](https://github.com/dotkernel/queue/network) |
| 13 | +[](https://github.com/dotkernel/queue/stargazers) |
| 14 | +[](https://github.com/dotkernel/queue/blob/main/LICENSE.md) |
90 | 15 |
|
91 | | -* Info about the [zlib_decode error](https://github.com/composer/composer/issues/4121). |
92 | | -* Info and solutions for [composer degraded mode](https://getcomposer.org/doc/articles/troubleshooting.md#degraded-mode). |
93 | | -
|
94 | | -## Application Development Mode Tool |
95 | | -
|
96 | | -This skeleton comes with [laminas-development-mode](https://github.com/laminas/laminas-development-mode). |
97 | | -It provides a composer script to allow you to enable and disable development mode. |
98 | | -
|
99 | | -### To enable development mode |
100 | | -
|
101 | | -**Note:** Do NOT run development mode on your production server! |
102 | | -
|
103 | | -```bash |
104 | | -$ composer development-enable |
105 | | -``` |
106 | | -
|
107 | | -**Note:** Enabling development mode will also clear your configuration cache, to |
108 | | -allow safely updating dependencies and ensuring any new configuration is picked |
109 | | -up by your application. |
110 | | - |
111 | | -### To disable development mode |
112 | | - |
113 | | -```bash |
114 | | -$ composer development-disable |
115 | | -``` |
116 | | - |
117 | | -### Development mode status |
118 | | - |
119 | | -```bash |
120 | | -$ composer development-status |
121 | | -``` |
122 | | - |
123 | | -## Configuration caching |
124 | | - |
125 | | -By default, the skeleton will create a configuration cache in |
126 | | -`data/config-cache.php`. When in development mode, the configuration cache is |
127 | | -disabled, and switching in and out of development mode will remove the |
128 | | -configuration cache. |
129 | | - |
130 | | -You may need to clear the configuration cache in production when deploying if |
131 | | -you deploy to the same directory. You may do so using the following: |
132 | | - |
133 | | -```bash |
134 | | -$ composer clear-config-cache |
135 | | -``` |
136 | | - |
137 | | -You may also change the location of the configuration cache itself by editing |
138 | | -the `config/config.php` file and changing the `config_cache_path` entry of the |
139 | | -local `$cacheConfig` variable. |
140 | | - |
141 | | -## Skeleton Development |
| 16 | +[](https://github.com/mezzio/mezzio-skeleton/actions/workflows/continuous-integration.yml) |
| 17 | +[](https://codecov.io/gh/dotkernel/queue) |
| 18 | +[](https://github.com/dotkernel/queue/actions/workflows/qodana_code_quality.yml) |
| 19 | +[](https://github.com/dotkernel/queue/actions/workflows/static-analysis.yml) |
142 | 20 |
|
143 | | -This section applies only if you cloned this repo with `git clone`, not when you |
144 | | -installed mezzio with `composer create-project ...`. |
| 21 | +## Installation |
145 | 22 |
|
146 | | -If you want to run tests against the installer, you need to clone this repo and |
147 | | -setup all dependencies with composer. Make sure you **prevent composer running |
148 | | -scripts** with `--no-scripts`, otherwise it will remove the installer and all |
149 | | -tests. |
| 23 | +Install `dotkernel/queue` by executing the following Composer command: |
150 | 24 |
|
151 | | -```bash |
152 | | -$ composer update --no-scripts |
153 | | -$ composer test |
| 25 | +```shell |
| 26 | +composer require dotkernel/queue |
154 | 27 | ``` |
155 | 28 |
|
156 | | -Please note that the installer tests remove installed config files and templates |
157 | | -before and after running the tests. |
| 29 | +## Documentation |
158 | 30 |
|
159 | | -Before contributing read [the contributing guide](https://github.com/mezzio/.github/blob/master/CONTRIBUTING.md). |
| 31 | +Documentation is available at: https://docs.dotkernel.org/queue-documentation |
0 commit comments