5fbd1dae30
bump the mysql memory limit
...
we hit this memory limit often in phabricator backup. this is all
very crude but should suffice for now.
2016-03-05 18:35:28 -08:00
057b89ab8e
Check error code of image removal
2015-10-15 14:06:05 -07:00
6b82fb9ddb
Remove old addon images on infra update
...
Fixes #329
2015-10-15 12:01:31 -07:00
f57c91847d
addons do not write to /var/log anymore
2015-10-15 11:00:51 -07:00
265ee15ac7
fix oldConfig madness
...
There is a crash when:
* App is configured. So, oldConfig now has {loc, access, portb }
* Cloudron is restored. The restore code path accesses the oldConfig.manifest.addons.
oldConfig is basically a messaging passing thing. It's not really a
db field. With that spirit, we simply pass an empty message in setup_infra.sh
2015-10-09 11:59:25 -07:00
0e8553d1a7
code path applies to upgraded cloudrons as well
2015-10-09 11:08:54 -07:00
bc7e07f6a6
mail: not required to expose port 25
2015-10-09 09:56:37 -07:00
eb1e4a1aea
mail now runs on port 2500
2015-10-09 09:29:17 -07:00
dc3e8a9cb5
mail now runs on port 2500
2015-10-09 09:13:28 -07:00
6ca040149c
run addons as readonly
2015-10-08 11:07:28 -07:00
5fcba59b3e
set memory limits for addons
...
mysql, postgresql, mongodb - 100m each
mail, graphite, redis (each instance) - 75m
For reference, in yellowtent:
mongo - 5m
postgresql - 33m
mysql - 3.5m
mail: 26m
graphite - 26m
redis - 32m
2015-09-14 13:47:45 -07:00
9266302c4c
Print graphite container id
2015-08-13 15:57:36 -07:00
755dce7bc4
fix graph issue finally
2015-08-13 15:54:27 -07:00
9dfaa2d20f
Create symlink in start.sh (and not container setup)
2015-08-13 15:36:21 -07:00
ed041fdca6
Put image names in one place
2015-08-12 19:38:44 -07:00
b8e4ed2369
Use latest images
2015-08-12 19:19:58 -07:00
74785a40d5
r -> ro (docker 1.7)
2015-08-10 21:14:28 -07:00
df9d321ac3
app.portBindings and newManifest.tcpPorts may be null
2015-07-20 00:10:36 -07:00
Girish Ramakrishnan