You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Social Web App Protocols (Notifications, Friends Lists, Followers and Following)
49
48
50
-
<!--
51
-
To read more about Solid, and which IETF and W3C specifications are used, visit: https://pdsinterop.org/solid-specs-overview/
52
-
-->
53
-
54
49
## Installation
55
50
56
51
To install the project, clone it from GitHub and install the PHP dependencies
@@ -67,21 +62,15 @@ At this point, the application is ready to run.
67
62
68
63
The PHP Solid server can be run in several different ways.
69
64
70
-
<!-- @TODO: Add local Dockerfile -->
71
-
72
65
The application can be run with a Docker image of your choice or on a local
73
66
environment, using Apache, NginX, or PHP's internal HTTP server. The latter is
74
67
only advised in development.
75
68
76
69
For security reasons, the server expects to run on HTTPS (also known as HTTP+TLS).
77
70
78
-
To run insecure, set the environment variable `ENVIRONMENT` to `develop`. This
79
-
will prohibit the application from running in production mode.
80
-
81
-
<!--
82
-
@TODO: Add single-button deploy scripts/config for Heroku, Glitch, and other
83
-
popular playgrounds/developer oriented service providers.
84
-
-->
71
+
To run insecure, for instance when the application is run behind a proxy or in a
72
+
PHP-FPM (or similar) setup, set the environment variable `PROXY_MODE`.
73
+
This will allow the application to accept HTTP requests.
85
74
86
75
### Docker images
87
76
@@ -209,71 +198,61 @@ The underlying functionality for these features is provided by:
209
198
210
199
## Development
211
200
201
+
The easiest way to develop this project is by running the environment provided
202
+
by the `docker-compose.yml` file. This can be done by running `docker-compose up`.
203
+
204
+
This will start the application and a pubsub server in separate docker containers.
205
+
212
206
### Project structure
213
207
214
208
This project is structured as follows:
215
209
216
-
<!--
217
-
.
218
-
├── build <- Artifacts created by CI and CLI scripts
219
-
├── cli <- CLI scripts
220
-
├── docs <- Documentation, hosted at https://pdsinterop.org/solid-server-php/
221
-
├── src <- Source code
222
-
├── tests <- Unit- and integration-tests
223
-
├── vendor <- Third-party and vendor code
224
-
├── web <- Web content
225
-
├── composer.json <- PHP package and dependency configuration
226
-
└── README.md <- You are now here
227
-
-->
228
210
```
229
211
.
230
-
├── src <- Source code
231
-
├── vendor <- Third-party and vendor code
232
-
├── web <- Web content
212
+
├── bin/ <- CLI scripts
213
+
├── config/ <- Empty directory where server configuration is generated
214
+
├── docs/ <- Documentation
215
+
├── src/ <- Source code
216
+
├── tests/ <- Test fixtures, Integration- and unit-tests
217
+
├── vendor/ <- Third-party and vendor code
218
+
├── web/ <- Web content
233
219
├── composer.json <- PHP package and dependency configuration
234
220
└── README.md <- You are now here
235
221
```
236
222
237
-
<!--
238
-
### Coding conventions
239
-
240
-
You can also run [php-cs-fixer](https://github.com/FriendsOfPHP/PHP-CS-Fixer) with the configuration file that can be found in the project root directory.
241
-
242
-
This project comes with a configuration file and an executable for [php-cs-fixer](https://github.com/FriendsOfPHP/PHP-CS-Fixer) (`.php_cs`) that you can use to (re)format your sourcecode for compliance with this project's coding guidelines:
243
-
244
-
```sh
245
-
$ composer php-cs-fixer fix
246
-
```
247
-
248
223
### Testing
249
224
250
225
The PHPUnit version to be used is the one installed as a `dev-` dependency via composer. It can be run using `composer test` or by calling it directly:
251
226
252
227
```sh
253
-
$ ./vendor/bin/phpunit
228
+
$ ./bin/phpunit
254
229
```
255
-
-->
256
230
257
231
## Contributing
258
232
259
-
Questions or feedback can be given by [opening an issue on GitHub](https://github.com/pdsinterop/php-solid-server/issues).
233
+
Questions or feedback can be given by [opening an issue on GitHub][issues-link].
260
234
261
235
All PDS Interop projects are open source and community-friendly.
262
236
Any contribution is welcome!
263
-
For more details read the [contribution guidelines](CONTRIBUTING.md).
237
+
For more details read the [contribution guidelines][contributing-link].
264
238
265
239
All PDS Interop projects adhere to [the Code Manifesto](http://codemanifesto.com)
266
-
as its [code-of-conduct](CODE_OF_CONDUCT.md). Contributors are expected to abide by its terms.
240
+
as its [code-of-conduct][code-of-conduct]. Contributors are expected to abide by its terms.
267
241
268
242
There is [a list of all contributors on GitHub][contributors-page].
269
243
270
-
For a list of changes see the [CHANGELOG](CHANGELOG.md) or the GitHub releases page.
244
+
For a list of changes see the [CHANGELOG][changelog] or [the GitHub releases page][releases-page].
271
245
272
246
## License
273
247
274
248
All code created by PDS Interop is licensed under the [MIT License][license-link].
0 commit comments