| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Replace the kkuleomi_config.rb file by the kkuleomi_config.rb.dist file,
when using docker-compose.yml or docker-compose.override.yml.
This is important as kkuleomi_config.rb is replaced by the
kkuleomi_config.rb.test whenever the tests are executed.
Consequently it is important to apply the kkuleomi_config.rb.dist
file again after the test have been run i.e. when running
docker-compose.yml or docker-compose.override.yml.
Signed-off-by: Max Magorsch <max@magorsch.de>
|
| |
|
|
|
|
|
|
|
|
|
| |
Update the project to Bootstrap 4, which is a major rewrite of the
entire project. So far, a Tyrian version that is based on Bootstrap 4
is included for that reason. However, in future, it may be retrieved
from the CDN or installed as node module.
Webpacker is bundeling all of the javascript code and stylesheets.
Signed-off-by: Max Magorsch <max@magorsch.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The asset pipeline was introduced in Rails 3.1. However, since Rails 5.1
webpacker has been available, so that it's possible to use webpack.
The project has been fully migrated to use webpacker for bundeling
javascripts as well as stylesheets now. This way, sprockets has been
completely replaced and removed from the project. Associated gems as
jquery-rails have been removed as well.
Accordingly all advanced webpack functionalities are available now.
The bin/first-run file as well as the Dockerfiles have been adjusted to
use webpacker instead of the asset pipeline.
Please note: In order to use webpacker, yarn has to be installed on
the target system. Please make sure that 'yarnpkg' is in your path.
Signed-off-by: Max Magorsch <max@magorsch.de>
|
| |\
| |
| |
| | |
Signed-off-by: Alec Warner <antarus@gentoo.org>
|
| | |
| |
| |
| |
| |
| |
| |
| | |
docker-compose can be used to deploy the application. The index will
be initialized and updated. Furthermore a cron job will be registered
for production environments to update the index every 10 minutes. °
Signed-off-by: Max Magorsch <max@magorsch.de>
|
| | |
| |
| |
| | |
Signed-off-by: Max Magorsch <max@magorsch.de>
|
| | |
| |
| |
| |
| |
| | |
Furthermore dejavu 3.4.0 will be used.
Signed-off-by: Max Magorsch <max@magorsch.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The newly added docker-compose.override.yml file overrides
settings in docker-compose.yml for development purposes. In
particular:
- the source code will be mounted into the container for
live reloading during the development
- dejavu is used as gui for elasticsearch for debugging
purposes
- cors is enabled in elasticsearch for usage with dejavu
These settings will automatically be used when executing:
$ docker-compose up
If you, however, don't want to use these settings (e.g. in
production) use:
$ docker-compose -f docker-compose.yml up
For further information please refer to:
https://docs.docker.com/compose/extends/#multiple-compose-files
Signed-off-by: Max Magorsch <max@magorsch.de>
|
|
|
The newly added docker-compose.override.yml file overrides
settings in docker-compose.yml for development purposes. In
particular:
- the source code will be mounted into the container for
live reloading during the development
- dejavu is used as gui for elasticsearch for debugging
purposes
- cors is enabled in elasticsearch for usage with dejavu
These settings will automatically be used when executing:
$ docker-compose up
If you, however, don't want to use these settings (e.g. in
production) use:
$ docker-compose -f docker-compose.yml up
For further information please refer to:
https://docs.docker.com/compose/extends/#multiple-compose-files
Signed-off-by: Max Magorsch <max@magorsch.de>
Signed-off-by: Alec Warner <antarus@gentoo.org>
|
Max Magorsch
Alec Warner
GitWeb