1f7b934d36
searx: fix #110
2017-02-22 13:40:08 +01:00
9856bd85d3
also update daily files
2017-02-22 02:39:04 +01:00
74c0f237fc
Update README.md
2017-02-22 02:34:23 +01:00
9c1ac64fb5
nextcloud: more confortable setup
2017-02-22 02:26:53 +01:00
bd3e5d94a9
boring-nginx: set ssl_dyn_rec_enable ( closes #129 )
2017-02-22 00:42:07 +01:00
58764d7722
update ghost dockerfile
2017-02-20 15:30:47 +01:00
2d65a8c5d0
Update README.md
2017-02-19 03:36:03 +01:00
a717c673ce
boring-nginx: add homemade tls1.3 patch
2017-02-19 03:34:27 +01:00
dd00c13965
Update README.md
2017-02-18 23:02:49 +01:00
178779142e
boring-nginx: dynamic tls records patch
2017-02-18 20:18:00 +01:00
3d5d826a63
Update Dockerfile
2017-02-18 20:07:34 +01:00
1e8350502e
Update Dockerfile
2017-02-18 19:59:27 +01:00
ae33feb556
SSE/SHA & AVX1 -> AVX2 ( #124 )
...
* SIMD-instructions support: AVX1 -> AVX2
* SIMD/SSE instructions for SHA
2017-02-18 18:03:55 +01:00
92dd056d85
boring-nginx: missing backslash
2017-02-18 17:31:40 +01:00
16f30bd6bd
BoringSSL/AVX2 to work on modern CPU ( #123 )
2017-02-18 17:30:47 +01:00
d3a6dd4e10
Update Dockerfile
2017-02-18 17:04:09 +01:00
7019cbc38a
nextcloud: add redis in daily
2017-02-18 16:55:45 +01:00
05c4d24baf
nextcloud: Fix missing Redis ( #122 )
...
* Update Dockerfile
* Update Dockerfile
* Update Dockerfile
* Update Dockerfile
2017-02-18 16:50:46 +01:00
2a7b6885f2
nextcloud: update gnu libiconv
2017-02-15 17:59:45 +01:00
db82d0ee39
boring-nginx: remove TLS 1.3 patch (not updated), nginx 1.11.10
2017-02-15 17:42:39 +01:00
72f7575f5d
Update README.md
2017-02-15 17:37:18 +01:00
c482784782
nextcloud: fix, php 7.1, remove redis
2017-02-15 17:36:36 +01:00
e3c4fa505b
missing backslash !
2017-02-15 15:13:09 +01:00
4d8fa9ed40
Add CRON_MEMORY_LIMIT ( #116 )
2017-02-15 15:12:09 +01:00
319ca5b4a3
chore(isso) : Missing { ( #111 )
...
Sorry ! :/ J'édits avec github c'est pas une bonne idée.
2017-02-05 04:41:02 +01:00
a9b18a57b5
isso: fix dockerfile
2017-02-02 18:14:23 +01:00
973929ba1a
chore(isso) : Update url source file ( #109 )
...
* chore(isso) : Update url source file
Le fichier source n'est pas un release mais une archive d'un tag donc l'url n'est pas bonne.
* Fix isntall pip
2017-02-02 13:06:23 +01:00
89727867fb
Merge pull request #108 from Hydrog3n/patch-1
...
chore(isso) : Update version for fix error
2017-02-01 21:38:31 +01:00
eee698afae
Update version for fix error
...
https://github.com/posativ/isso/commit/339318eb92de173d405cbf20843e0df386f855ca
2017-02-01 21:26:35 +01:00
3396da1060
boring-nginx: update nginx to 1.11.9
2017-01-25 18:19:15 +01:00
ed609cb68e
Update README.md
2017-01-22 14:41:49 +01:00
0f598f5a8a
rtorrent-flood: chown flood-db dir
2017-01-22 05:25:36 +01:00
7ad70b9f01
rtorrent-flood: fix previous commit, change volume
2017-01-22 05:23:15 +01:00
0c396e9d96
fix chown ( closes #103 )
2017-01-22 02:57:17 +01:00
4859a5e5f2
nextcloud: fix chown
2017-01-22 02:49:39 +01:00
8ec09b74a0
nextcloud: fix #102
2017-01-22 02:48:30 +01:00
998ef53d70
boring-nginx: update ssl_params (old ChaCha20-Poly1305 removed from boringssl)
...
https://boringssl.googlesource.com/boringssl/+/2e839244b078205ff677ada3fb83cf9d60ef055b
2017-01-20 02:46:50 +01:00
06cb9d839b
MAINTAINER is deprecated
2017-01-19 02:31:59 +01:00
85fd16739d
rtorrent-flood: fix torrent upload issue
2017-01-18 15:53:39 +01:00
68ab88e2a8
piwik: fix chown
2017-01-18 15:13:25 +01:00
e1175e7e14
searx: based on alpine edge
2017-01-18 04:14:55 +01:00
d9624ffc76
Update README.md
2017-01-18 04:04:07 +01:00
a21a6dc875
boring_nginx: remove spdy from vhost sample
2017-01-18 03:46:19 +01:00
8c1cc7e4a8
rtorrent-flood: fix filebot handshake failure
2017-01-18 02:55:23 +01:00
707af67a86
rtorrent-flood: add mediainfo, alpine 3.5
2017-01-17 23:55:28 +01:00
33a9a79065
nextcloud: fix chown ( closes #89 )
2017-01-17 19:22:57 +01:00
1de4580cb5
rtorrent-flood: fix chown
2017-01-17 04:19:10 +01:00
ab39863e70
Merge pull request #98 from ConorIA/patch-1
...
Be noisy about updating permissions
2017-01-16 22:44:16 +01:00
18d29d7dbf
Be noisy about updating permissions
...
In #75 , I mentioned that I was a little stumped why my Nextcloud container was showing a `502 Bad Gateway` error. In the end, it turned out that it was just updating the permissions in the container, which are set to `nobody:nogroup`, but need to be chowned to `991:991` when first starting a fresh container. This PR seeks to make that a little more obvious to the user, in case they choose to use `docker-compose logs -f nextcloud` or such.
2017-01-16 16:32:16 -05:00
321e04e9d5
clean up
2017-01-16 22:15:10 +01:00
Wonderfall
Wonderfall
Denis Denisov
Berndinox
Lorenz Brun
Loïc Vaillé
Conor Anderson