13b8963076
readme: added `Accessing your Tomcat server from the host` section
2015-08-13 19:49:00 +05:30
a8f87c5268
readme: added `Deploying web applications on Tomcat` section
2015-08-13 19:45:47 +05:30
856667707e
basic readme
2015-08-13 19:17:49 +05:30
cc09b9d041
display application credentials even when `TOMCAT_PASSWORD` is not specified
2015-08-13 13:36:06 +05:30
39ba0ff825
update `sed` command to set `TOMCAT_PASSWORD`
2015-08-13 13:30:47 +05:30
f888cb7e2a
symlink contents of `$BITNAMI_APP_DIR/webapps.defaults/` instead of copying them to `/app/`
2015-08-13 10:27:54 +05:30
fdf500092f
fix `/app` symlink
2015-08-13 10:27:33 +05:30
94b27ce290
added .dockerignore
2015-08-13 00:37:20 +05:30
43107d080f
moved `BITNAMI_APP_VOL_PREFIX/webapps/` to `/app/`
2015-08-13 00:35:40 +05:30
db4021c8ed
comments!
2015-08-12 23:44:57 +05:30
41ea1e582b
replaced `/app` volume with `$BITNAMI_APP_VOL_PREFIX/webapps` volume
...
Users can drop the `.war` files of their applications into this
directory and Tomcat will automatically pick them up.
2015-08-12 23:40:09 +05:30
249f4983aa
removed accidentally committed `COPY` instruction
2015-08-12 22:46:08 +05:30
5b2ce7b70d
added `/app` volume
2015-08-12 22:42:31 +05:30
87676eedb2
start `catalina.sh` as user `tomcat`
2015-08-12 22:39:42 +05:30
662bac1094
always `chown` the `conf` and `log` directories
2015-08-12 22:39:38 +05:30
3a00f05982
intial creation
2015-08-12 22:39:16 +05:30
90116b2396
replication without any downtime
2015-08-12 13:49:47 +05:30
b37908144d
output formatting
2015-08-12 13:49:47 +05:30
de21f71bf8
add `--log-bin=mysql-bin` to `master` only
2015-08-12 13:49:47 +05:30
bc3a8f788b
give `MARIADB_USER` all the required rights to do a `mysqldump`
2015-08-12 13:49:47 +05:30
b9380a0f61
fix `mysqldump` output so that it is compatible with the `--init-file` option
2015-08-12 13:49:47 +05:30
da687232d6
configure `mysqldump` to add the `SLAVE START` statement
2015-08-12 13:49:47 +05:30
4cf7c4702b
configure the MASTER_HOST before taking the dump
...
If you specify the `MASTER_HOST` or `MASTER_PORT` option, the slave assumes
that the master server is different from before (even if the option
value is the same as its current value.) In this case, the old values
for the master binary log file name and position are considered no
longer applicable, so if you do not specify `MASTER_LOG_FILE` and
`MASTER_LOG_POS` in the statement, `MASTER_LOG_FILE=''` and `MASTER_LOG_POS=4`
are silently appended to it.
Do avoid the resetting of `MASTER_LOG_FILE` and `MASTER_LOG_POS`, we
generated the dump after setting the `MASTER_HOST`
https://dev.mysql.com/doc/refman/5.0/en/change-master-to.html
2015-08-12 13:49:47 +05:30
993b16471e
added master/slave replication support
...
Example,
Start master:
```bash
docker run -it --rm --name mariadb-master \
-e 'MARIADB_USER=root' -e 'MARIADB_PASSWORD=password' \
-e 'MARIADB_DATABASE=newdatabase' \
-e 'REPLICATION_MODE=master' -e 'REPLICATION_USER=slave' -e 'REPLICATION_PASSWORD=slavepassword' \
bitnami/mariadb
```
Start Slave:
```bash
docker run -it --rm --name mariadb-slave \
--link mariadb-master:mariadb-master \
-e 'MARIADB_USER=root' -e 'MARIADB_PASSWORD=password' \
-e 'MARIADB_DATABASE=newdatabase' -e 'REPLICATION_MODE=slave' \
bitnami/mariadb
```
2015-08-12 13:49:47 +05:30
b596ffdb63
remove the config files generated by `initdb` at database initialization
2015-08-12 11:53:04 +05:30
2614cb8be9
populate configuration templates in `conf.defaults` at `post-install`
2015-08-12 11:52:29 +05:30
20327c7452
do not move `postgresql.auto.conf` to `conf` volume
2015-08-12 11:49:34 +05:30
a72915f127
do not create symlinks to config files
2015-08-12 11:47:55 +05:30
157a3f91ca
fix shebang
2015-08-12 11:45:10 +05:30
73b23d08af
readme: cleanups
2015-08-11 12:49:04 +05:30
37bb30a457
added README
2015-08-11 12:47:27 +05:30
59725356e3
use path to `postgresql.conf` in `conf` volume in `PROGRAM_OPTIONS`
2015-08-11 12:33:43 +05:30
ecbb8eeef4
Merge pull request #18 from bitnami/5.5.45-0
...
Bump version 5.5.45-0
2015-08-10 13:05:57 -07:00
173b1d5efd
Bump version 5.5.28-0
2015-08-10 12:07:57 -07:00
1232c90b27
Bump version 5.5.45-0
2015-08-10 12:04:51 -07:00
24c6a7c02e
Merge branch 'conf-volume'
2015-08-10 23:44:05 +05:30
1eb940dad0
added `conf` volume
2015-08-10 23:42:16 +05:30
7f344811f2
fix typo
2015-08-10 23:28:41 +05:30
c8fd8ab5bf
Merge branch 'tests'
2015-08-10 23:20:24 +05:30
f97638d156
tests: "Data gets generated in data and logs if bind mounted in the host"
2015-08-10 23:18:07 +05:30
9a8f8225e6
tests: "All the volumes exposed"
2015-08-10 23:15:22 +05:30
d60f22808a
tests: "If host mounted, password and settings are preserved after deletion"
2015-08-10 23:13:03 +05:30
574237beb5
tests: "User and password settings are preserved after restart"
2015-08-10 23:10:37 +05:30
44f7753886
"Create custom user and database with password"
2015-08-10 23:10:37 +05:30
199f410130
tests: "Can't create a custom user without database"
2015-08-10 23:10:37 +05:30
2f7811a1ef
tests: "Custom database created"
2015-08-10 23:10:37 +05:30
3ee474a745
tests: "User postgres is superuser"
2015-08-10 23:10:37 +05:30
3bfc8feaf5
tests: "User postgres created with password"
2015-08-10 23:10:37 +05:30
7dfde6e416
tests: "Port 5432 exposed and accepting external connections"
2015-08-10 23:10:37 +05:30
132ba9bbf8
`chown` the `data` directory before calling `initdb`
...
since `initdb` is launched as the `postgres` user, we need to ensure
that the `data` directory is owned by the `postgres` user
2015-08-10 23:09:41 +05:30
Sameer Naik
Miguel Ángel Martínez Triviño
Miguel Martinez