
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 6 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: deployment.
Looking up deployment tag. Showing 6 results. Clear
Saved by uncleflo on January 27th, 2022.
Putting Raspberry Pi boards into space is nothing new, but the method of achieving orbit often differs. While the Astro Pi computers headed for the final frontier onboard a SpaceX Falcon 9 rocket, there are some decidedly lower-tech approaches including, as detailed on the Tindie blog, this $45 RP2040 flight computer from Finnish designer Dan Invents. Combining the RP2040 controller with an altimeter, accelerometer, temperature sensor, and enough juice to power two servo motors (for parachute deployment on the way down), the Rockit (rocket operation computing kit) weighs just 0.18oz (5g) and measures 1.73 x 0.9 x 0.35 inches (44 x 22 x 9 mm). It comes with an open-source firmware pre-installed, and can be tinkered with and updated over micro USB. There's a 16-position rotary switch for adjusting parameters such as start and end positions for the servos, and also a buzzer, so you can more easily find your rocket after a successful landing. Compared to the 2MHz Apollo guidance computer that deposited Neil Armstrong on the Moon, the RP2040 is a powerhouse, and should be more than capable of altitude-based parachute opening and logging flight data from the sensors to a micro SD card. The kit, which costs $44.99, comes with just the board and its pin headers - you need to supply your own battery, servos, cabling, micro SD card and space suit.
accelerometer altimeter servo micro raspberry pi firmware parachute rocket logging kit hardware tips pin documentation deployment orbit guidance altitude board card test project build create DIY introduction description power propel electronics control fly space sky
Saved by uncleflo on July 24th, 2019.
Many customers want a disaster recovery environment, and they want to use this environment daily and know that it's in sync with and can support a production workload. This leads them to an active-active architecture. In other cases, users like Netflix and Lyft are distributed over large geographies. In these cases, multi-region active-active deployments are not optional. Designing these architectures is more complicated than it appears, as data being generated at one end needs to be synced with data at the other end. There are also consistency issues to consider. One needs to make trade-off decisions on cost, performance, and consistency. Further complicating matters is the variety of data stores used in the architecture results in a variety replication methods. In this session, we explore how to design an active-active multi-region architecture using AWS services, including Amazon Route 53, Amazon RDS multi-region replication, AWS DMS, and Amazon DynamoDB Streams. We discuss the challenges, trade-offs, and solutions.
disaster aws recovery environment day sync production workload architecture netflix geography region deployment design consistent complication performance store replication method session amazon route data rds challenge trade solution multi-region administration youtube movie guide
Saved by uncleflo on May 12th, 2019.
Every organization which has adopted DevOps practices wants to quickly adopt "Continuous" everything, be it Integration, Deployment, Testing or, Monitoring. For a successful DevOps operation, CI/CD is very important for any small or big size organization to shorter development cycles and innovate faster, reduce deployment failures, safe Rollbacks and reduce MTTR (mean time to recover). In this article, we will uncover a new way of bringing continuous integration and continuous delivery of applications to your Kuberenetes cluster. We are using Jenkins as the CI tool which will poll the Git repositories to build Docker images on commits and push it to Docker registry. We will use Spinnaker as the CD tool which continuously polls the Docker registry and triggers the deployment pipelines to update applications in your Kubernetes cluster.
spinnaker rollback innovate node azure folder deployment registry orchestration deploy cluster indexing setup configure cloud pipeline commit continuous install provider integration storage tool container server gateway process developer development workflow toolchain repository docker image cycle failure kubernetes administration policy company business
Saved by uncleflo on December 27th, 2017.
You've got your Rails or Rack-based Ruby app built. It's even running in Docker off your laptop and other developers on your team have it up-and-running as well. Everything looks good, so time to ship it. Wait! Not so fast! Transitioning to a Docker production environment isn't quite as easy as it sounds. There's more to it than just shipping your locally built container image into a production environment. Let's examine the 9 most critical decisions you'll face before you can securely deploy your Dockerized Rails and Rack-based Ruby apps into production:
docker software reasoning examination environment deployment production development administration webserver server deploy ship workflow guide explanation article
Saved by uncleflo on December 27th, 2017.
At the first Docker Helsinki Meetup for 2017 on January 17th, we heard about three interesting use cases of the ins and outs of how Docker is used in production at Solita, Zalando and Pipedrive. We also heard about the good, the bad and the ugly of running Docker in production. Solita's Use Case: Firstly, Heikki Simperi from Solita explained how his company uses Docker to handle the various apps and systems associated with their management of the Finnish National Railway Service (VR), as well as the problems they've run into when using Docker. Solita runs a variety of their own apps on Docker, including a navigator for train drivers, a construction notification system and a traffic controller app. Heikki reiterated that it's important for the downtime to be minimal when the apps involved are ones responsible for railway management and that "anything over a 3-5 min downtime causes delays for trains, but nobody dies". Most of the issues they experienced using Docker were related to building an image, having a private repository, removing or starting up a container, or a bug inside an app. Overall, the running usage of the Docker platform has been stable, with "zero downtime". The problems have lessened after upgrading to each new Docker version and they are experiencing less and less problems as time goes on. They are looking forward to the release of Docker 1.12 on a stable channel from Red Hat.
kontena docker production use case case system it information system app management experience downtime involvement release process workflow development administration guide howto business company enterprise corporation large extensive deployment security patch container image hub pipeline tools configuration script file test distribution linux engine option
Saved by uncleflo on October 20th, 2016.
Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows. Capistrano can be used to: Reliably deploy web application to any number of machines simultaneously, in sequence or as a rolling set; To automate audits of any number of machines (checking login logs, enumerating uptimes, and/or applying security patches); To script arbitrary workflows over SSH; To automate common tasks in software teams; To drive infrastructure provisioning tools such as chef-solo, Ansible or similar. Capistrano is also very scriptable, and can be integrated with any other Ruby software to form part of a larger tool.
remote administration automation script deployment application reliable machine server patch workflow audit security provision ruby software tool manage development business control
No further bookmarks found.