Ryan Glover
Ryan Glover
Would be best to do this as `joystick[log|warn|error|info]('something', ['development'])` where the second argument is an array of environments to log the message in. If no environments are passed, it's assumed...
For any existing API options that leverage camelCase (e.g., accounts APIs with `emailAddress`), leave that as an option but prefer `email_address` in the docs and support it internally.
Done. Where appropriate, the legacy camelCase is still supported.
Chaos = having a cron job executing on multiple nodes simultaneously.
It'd likely be best to have a master list of these in the top 5-10 languages worldwide built in to the framework.
This should also work with Push. Ideally you could do `joystick push static` and it would prompt you to choose a destination (either an IP, S3 bucket, etc).
Not sure this is as easy as it seems. Hypothetically, yes, but you'd have to hit every route in the app, generate the HTML/CSS/JavaScript, and assume that the data it's...
Just whipped up a bespoke rate limiter that can be DB backed pretty easily. See the Mod v2 repo for this. We'll want to adapt it using the query map...
I'd want to be able to see: - Each request that's run (verbose mode?) - The timeline (animated so I can get a feel for race conditions and o(n) problems)...
Ideally, we do this as scripts that can be run via `joystick test load --script scriptNameInTestsFolder`. That way you can write individual load tests and get the results back in...