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
@@ -15,27 +15,41 @@ Chamilo is an e-learning platform, also called "LMS", published under the GNU/GP
15
15
16
16
## Quick install
17
17
18
-
**Chamilo 2.0 is still in development. This installation procedure below is for reference only. For a stable Chamilo, please install Chamilo 1.11.x. See the 1.11.x branch's README.md for details.**
18
+
**Chamilo 2.0 is still in development. The installation procedure below is for reference only. For a stable Chamilo, please install Chamilo 1.11.x. See the 1.11.x branch's README.md for details.**
19
19
20
-
### Minimum server hardware requirements
20
+
### Minimum hardware requirements
21
21
22
-
Chamilo 2.0 has been tested on a 2 vCPUs, 2GB RAM virtual machine under Ubuntu 24.04 and has been shown to work.
22
+
#### Server
23
+
24
+
You will need (short version):
25
+
- 2 vCPUs
26
+
- 4GB RAM
27
+
- 4GB free disk space
28
+
29
+
Chamilo 2.0 has been tested on a 2 vCPUs, 2GB RAM virtual machine under Ubuntu 24.04 and has been shown to work, but to
30
+
build the development environment, you will need at least 4GB RAM.
23
31
At this stage, we haven't made any load testing to evaluate the number of users that could use the system simultaneously.
24
32
Remember this is an alpha version. As such, it will run in "dev" mode (see the `.env` file), considerably more slowly the "prod" mode.
25
33
34
+
#### Client
35
+
36
+
Any recent computer with a recent (no older than 5y) browser should do.
Another option to install Node.js is by using NVM (Node Version Manager). You can install it following the instructions [here](https://github.com/nvm-sh/nvm#installing-and-updating).
176
+
Alternative (not recommended): install Node.js by using NVM (Node Version Manager). You can install it following the
We do not recommend running composer as the root user!
158
-
When asked whether you want to execute the recipes or install plugins for some of the components, you can safely type 'n' (for 'no').
214
+
When asked whether you want to execute the recipes or install plugins for some of the components,
215
+
you can safely type 'n' (for 'no').
159
216
160
217
~~~~
161
218
yarn set version stable
@@ -166,9 +223,11 @@ sudo touch .env
166
223
sudo chown -R www-data: var/ .env config/
167
224
~~~~
168
225
169
-
In your web server configuration, ensure you allow for the interpretation of .htaccess (`AllowOverride all` and `Require all granted`), and point the `DocumentRoot` to the `public/` subdirectory.
226
+
In your web server configuration, ensure you allow for the interpretation of .htaccess (`AllowOverride all` or
227
+
`Require all granted`), and point the `DocumentRoot` to the `public/` subdirectory.
170
228
Finally, make sure your PHP config points at Redis for sessions management.
171
-
This should look similar to this very short excerpt (in your Apache vhost block):
229
+
This should look similar to the short excerpt below (in your Apache vhost block) if you use SSL.
230
+
If you do not use SSL, you can remove the first block and change `*:443` by `*:80` for the second block.
ad the URL you have defined for your host, e.g. https://my.chamilo.net(this should redirect you to `main/install/index.php`) and follow the UI instructions (database, admin user settings, etc).
264
+
Once the above is ready, use your browser to load the URL you have defined for your host, e.g. https://my.chamilo.net
265
+
(this should redirect you to `main/install/index.php`) and follow the UI instructions (database, admin user settings, etc).
207
266
208
267
After the web install process, change the permissions back to a reasonably safe state:
209
268
~~~~
210
-
chown -R root .env config/
269
+
chown -R root: .env config/
211
270
~~~~
212
271
213
-
## Quick update for development/testing purposes
272
+
## Quick updates for development/testing purposes
214
273
215
274
If you have already installed it and just want to update it from Git, do:
This will respect the migration logic and do the required data processing.
301
+
You can see the version numbers in the list of updated or created files when launching `git pull`.
237
302
238
-
The commands above will update the JS (yarn) in public/build/ and PHP (composer) dependencies in vendor/.
239
-
240
-
Sometimes there are conflicts with existing files so, to avoid those, here are some hints :
241
-
- for composer errors, you can remove the vendor folder and composer.lock file
242
-
- for yarn errors, you can remove yarn.lock .yarn/cache/* node_modules/*
243
-
- when opening Chamilo, if the page does not load, then you might want to delete var/cache/*
303
+
Som`e updates might (rarely) cause conflicts with existing files so, to avoid those, here are some hints :
304
+
- for composer errors, you can remove the vendor folder and composer.lock file, then launch `composer update`
305
+
- for yarn errors, you can remove yarn.lock .yarn/cache/* node_modules/* and launch `yarn up`
306
+
- when opening Chamilo, if the page does not load, then you might want to delete var/cache/* or launch `php bin/console cache:clear` from the root of Chamilo
244
307
245
308
### Refresh configuration settings
246
309
@@ -371,21 +434,24 @@ following commands can be used.
* in general, the main/ folder has been moved to public/main/
377
-
* a big part of the frontend has been migrated to VueJS + Tailwind CSS
378
-
* app/Resources/public/assets moved to public/assets
379
-
* main/inc/lib/javascript moved to public/js
380
-
* main/img/ moved to public/img
381
-
* main/template/default moved to src/CoreBundle/Resources/views
382
-
* src/Chamilo/XXXBundle moved to src/CoreBundle or src/CourseBundle
383
-
* bin/doctrine.php removed use bin/console doctrine:xyz options
384
-
* Plugin images, CSS and JS libs are loaded inside the public/plugins folder
385
-
(composer update copies the content inside plugin_name/public inside web/plugins/plugin_name
386
-
* Plugins templates use the ``asset()` function instead of using "_p.web_plugin"
387
-
*`main/inc/local.inc.php` has been removed
388
-
* Translations are managed through Gettext
437
+
## Big changes from 1.x (for developers)
438
+
439
+
This is a list of structural changes to help developers/maintainers of Chamilo 1.11 find their way in Chamilo 2. It is *not* a features list (refer to `public/documentation/changelog.html` for that).
440
+
441
+
* in general, the `main/` folder has been moved to `public/main/`
442
+
* a big part of the frontend has been migrated to VueJS + Tailwind CSS (see `assets/vue/`)
443
+
*`app/Resources/public/assets/` moved to `assets/`
444
+
*`main/inc/lib/javascript/` moved to `assets/js/`
445
+
*`main/img/` moved to `public/img/`
446
+
*`main/template/default/` moved to `src/CoreBundle/Resources/views/`
447
+
*`src/Chamilo/XXXBundle/` moved to `src/CoreBundle/` or `src/CourseBundle/`
448
+
*`bin/doctrine.php` removed, use `bin/console doctrine:xyz` options
449
+
* plugin images, CSS and JS libs are loaded inside the `public/plugin/` folder and the folder names have been renamed to CamelCase
450
+
* plugins templates use the `asset()` function instead of using `_p.web_plugin`
451
+
*`main/inc/local.inc.php` has been removed and `main/inc/global.inc.php` greatly reduced
452
+
* translations are managed through Gettext, from the `translations/` directory for PHP code and from `assets/locales/` for VueJS code
453
+
* files in `app/config/` have been restructured (to `.yaml`) and moved to `config/`
454
+
*`app/config/configuration.php` has essentially been emptied to the `settings` table (accessible via the admin page in Chamilo), while the critical settings (database access etc) have been transferred to `.env`
389
455
390
456
Libraries
391
457
@@ -432,9 +498,10 @@ See https://github.com/chamilo/chamilo-lms/projects/3
432
498
If you want to submit new features or patches to Chamilo 2, please follow the
0 commit comments