Been using Docker with SS4 for a while, see https://github.com/gordonbanderson/flossydock/tree/silverstripe4 (based on Laradock)
sudo docker-compose up -d nginx workspace memcached mariadb mailhog to kick it off, place your silverstripe project at ../www
I've only updated the 7.2 workspace Dockerfile though
a simple option is to place this in your web root as docker-compose.yml
- version: '2'
- image: brettt89/silverstripe-web:7.1-platform
- working_dir: /var/www
- - .:/var/www/html
- - "80:80"
- image: mariadb
- restart: always
- - MYSQL_ALLOW_EMPTY_PASSWORD=true
sudo docker-compose up -d web database should get you a site up and running
did github's security flaw cause everyones password to reset, or just a few?
there’s a SitemapPage in cwp that can be easily ported to SS4
- Hi there,
- During the course of regular auditing, GitHub discovered that a recently introduced bug exposed a small number of users’ passwords to our internal logging system, including yours. We have corrected this, but you'll need to reset your password to regain access to your account.
- GitHub stores user passwords with secure cryptographic hashes (bcrypt). However, this recently introduced bug resulted in our secure internal logs recording plaintext user passwords when users initiated a password reset. Rest assured, these passwords were not accessible to the public or other GitHub users at any time. Additionally, they were not accessible to the majority of GitHub staff and we have determined that it is very unlikely that any GitHub staff accessed these logs. GitHub does not intentionally store passwords in plaintext format. Instead, we use modern cryptographic methods to ensure passwords are stored securely in production. To note, GitHub has not been hacked or compromised in any way.
It’s just a pagetype, rather than a module. One sec
aka "Github intended to store your password as bcrypt, but we ended up just saving them as plain text"