uncleflo
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 2 bookmarks
howto information development guide reference administration design website software solution online service product business uk tool company linux code server application system web list video marine create data experience tutorial description explanation learn technology build article blog world project boat download windows lookup security free performance javascript technical london beautiful control network tools support course file research purchase image library programming youtube example php construction install opensource community html quality computer feature profile power browser music platform process mobile work user share manage professional database hardware buy industry advice internet dance developer installation search 3d camera customer access travel material standard money test develop documentation review css engineering photography webdesign engine device digital speed event api source management question program client phone discussion content simple story water marketing yacht app account setup interface package idea fast communication compare cheap script market study easy live google resource operation demonstration contact startup
Tag selected: sandbox.
Looking up sandbox tag. Showing 2 results. Clear
How are you guys handling QA environments on AWS? : aws
Saved by uncleflo on July 11th, 2019.
News, articles and tools covering Amazon Web Services (AWS), including S3, EC2, SQS, RDS, DynamoDB, IAM, CloudFormation, Route 53, CloudFront, Lambda, VPC, Cloudwatch, Glacier and more. Just a curiosity. At this point I've done: single staging environment for small teams, and that obviously doesn't work well beyond a couple; one off EC2 instances that just use docker to make a mini-replicated environment; cloudformation to spin up an entire, and yet smaller, version of our production; ngrok and just having our QA test directly. The area I'm interested to see how people are handling it is with respect to data. Are you replicating the full DB? Just using in memory and some seed data? Additionally, for those of you that have this (or have had one in the past), how did you guys set it up to be "pleasurable" to work with? By that I mean it not being some long winding rube goldberg machine that almost defeats the purpose of having a CI.
sandbox setup snapshot replication deploy stack account environment instance control machine aws amazon production quality assurance handle administration howto guide read forum question team
No further bookmarks found.