uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 2 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile user process work database share manage hardware professional buy industry internet dance advice installation developer 3d search access material customer camera travel test standard review documentation css money engineering develop webdesign engine device photography digital api speed source program management phone discussion question event client story simple water marketing app yacht content setup package fast idea interface account communication cheap compare script study live market easy google resource operation startup monitor training
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.