Improve code comment
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 24 2016
Jan 23 2016
- -------------------------------------------------------------
- Notifications center
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Author: Sébastien Santoro aka Dereckson
- Project: Nasqueron
- Created: 2016-01-23
- Description: Listen to webhooks, fire notifications to
# the broker. Used for CI / IRC notifications.
- Image: nasqueron/notifications
- Services used: RabbitMQ broker (white-rabbit)
- Docker volume (/data/notifications/storage)
- -------------------------------------------------------------
Dwellers is already in the whitelist.
BROKER_HOST=white-rabbit.nasqueron.org BROKER_USER=`ssh -i /root/.ssh/id_zr zr@ysul.nasqueron.org getcredentials 56 username` BROKER_PASS=`ssh -i /root/.ssh/id_zr zr@ysul.nasqueron.org getcredentials 56` BROKER_VHOST=dev
Credentials created on the broker and saved at K56.
Jan 22 2016
More robust .env code
When .env doesn't exist, it executes what it should (echo "APP_KEY=SomeRandomString" > .env then php artisan key:generate but the command doesn't update .env.
Perfect, every test making requests failed with RuntimeException: No supported encrypter found. The cipher and / or key length are invalid..
See also rNOTIF53de6354a0b3, which allowed the site to run without any exception in this scenario.
T690 shows why this commit, created to facilitate CI configuration, were a rather bad idea.
Actually, the application itself creates a security risk with a default valid key. That will be SomeRandomString.
SomeRandomString actually won't work.
Lack of application key
All is done and moved, but the domain name tazaouaght.com has been lost.