Following work this week by @Sandlayth (Dwellers) and me (Ysul), all *.nasqueron.org sites are migrated to Let's encrypt certificates.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 4 2016
Still actively developed, as shown on https://github.com/matrix-org and a GSoC participation.
Notifications are set up for DevCentral and GitHub, to #wolfplex only as we don't support multichannel currently, and we don't currently monitor TrustSpace as operations level.
01:10:57 < Wearg> dereckson accepted D394: Arcanist configuration.
01:11:29 < Wearg> dereckson committed Arcanist configuration — https://github.com/trustspace/www/commit/097733ec7845e84a453c6fc743f7a09fe3df89d1
01:11:37 < Wearg> dereckson closed D394: Arcanist configuration by committing rTSWWW097733ec7845: Arcanist configuration.
01:11:39 < Wearg> dereckson committed rTSWWW097733ec7845: Arcanist configuration (authored by dereckson).
| tmp | Quick tests or invalid attic experiments |
| dist | Scripts shipped with the eggdrop |
| vendor | Third party scripts, not integrated, currently only bseen |
| Maintenance | One shot scripts to populate config, could contain personal data |
| private | Code to maintain some servers/db stuff |
Rebased against rVIPER head.
Jun 3 2016
$ git reset --hard c91a0a8b9faa $ git push Counting objects: 30, done. Delta compression using up to 4 threads. Compressing objects: 100% (24/24), done. Writing objects: 100% (30/30), 4.89 KiB | 0 bytes/s, done. Total 30 (delta 18), reused 10 (delta 6) To git@github.com:nasqueron/viperserv.git 27c6b0d..c91a0a8 master -> master
Doesn't work currently. We need to debug that.
GitHub → Notifications center
A restart of redis-server have resolved the problem
Created a branch nasqueron_deploy on git@github.com:dereckson/hotglue2.git
Should normally definitively fixed with this:
Another thing to test: SuEXEC AP_DOC_ROOT should be /var/wwwroot.
So for reference, we can now customize SuEXEC settings.
docroot switched back to /usr/local/www/data
Still the same error:
Jun 2 2016
Improve Docker command, so out of the box Docker installation won't expose the port to world.
In D25#6159, @xcombelle wrote:@dereckson Yes it's ok I would just nitpick that the line in the example of the README -e TRUST_ALL_PROXIES=1 \ is an unecessary example of unsecure use and a better line would be -e TRUST_ALL_PROXIES=0\ But that is really too much nitpicking for saying no to the patch
Jun 1 2016
@dereckson Yes it's ok I would just nitpick that the line in the example of the README -e TRUST_ALL_PROXIES=1 \ is an unecessary example of unsecure use and a better line would be -e TRUST_ALL_PROXIES=0\ But that is really too much nitpicking for saying no to the patch