I was deeply into it as well (though not at your level). I was so happy when a question I asked was printed in Action Pursuit Games (something like should I upgrade to nitro or stay with CO2?).
They weren't late, though? If they wanted people to show up 5-10 minutes early, make the training at 5:50 or 5:55. Don't say 6 and really mean earlier.
Wow this is awesome. I had to integrate Alipay into a checkout process in ~2010 and it was a complete nightmare - and not even as a result of the language barrier. The API was just so so bad. Glad this is in Stripe now.
I generally agree, but if the retailer is large enough they almost certainly pay a percentage of their cash payments to a Brinks-like company to securely handle the transfer of the money.
I want to know an explanation of why credit card data was stored. Is this standard? Shouldn't they only need it long enough to process the transaction - there's no reason to store it, correct?
Was the data stolen in transit (should be entirely encrypted) or stolen while at rest?
I'm of the same opinion. I host all of my production apps on Linode (the 8 cores is nice too), and my staging environment is on DO. I don't mind paying more for Linode because I think their network is better.
All of my repo's have a 'build-dev' script in the root of the repository (see here: https://github.com/brightmarch/picto/blob/master/build-dev). Run that after you pull it down and it builds the environment for you (minus setting up Vagrant).
You should commit your asset files in the Bundle, but not the ones in web/bundles/ because those are created by copying or symlinking the assets in your Bundle.
You have some usernames and passwords (to what looks like production servers) sprinkled throughout your app. May need to change those ASAP, wipe your history, or something.
Lots of suggestions:
* Don't write your own cron scripts, use Symfony Commands.
* Delete the Acme Bundle.
* Don't store your vendor directory in Git! Completely unnecessary and waste of 47MB.
* Don't commit parameters.yml, that's what parameters.yml.dist is for.
* Use a migration tool (Doctrine Migrations are fine) instead of one big SQL dump.
* Not sure what mongodb/example.php is for.
* Why is all the plivo stuff in web/plivo/ instead of being a callable controller?
* Are you manually generating your Doctrine entities?
* Don't commit your asset directories (they should be symlinks).
* No need to use PHPMailer (or include the entire project in your repository), Symfony comes with Swiftmailer which is great.
The design looks great, but I wouldn't trust a lot of this (especially after seeing how many hosts and usernames and passwords you left scattered about).
It hasn't made me rich, but it usually sells about a copy a day. I love that it's entirely passive. I wrote it, published it, and it just sits there on my website making money.
It's also been a good way to build a list of people who would be interested in other things I make.
PS. Use coupon code "hn" for $2 off if you're interested.