
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 control network beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community profile computer feature power browser music platform mobile work user process manage database share hardware professional buy industry internet dance advice installation developer 3d camera search access customer travel material test standard money documentation review css engineering webdesign engine develop device photography digital api speed source program management phone discussion question event client story simple water marketing yacht app content setup package fast idea interface account communication cheap script compare study market easy live google resource operation startup monitor training
Tag selected: patch.
Looking up patch tag. Showing 6 results. Clear
Saved by uncleflo on February 26th, 2018.
At work, we run a simple high-availability (HA) MariaDB setup that consists of an active master that handles all read and write queries from our applications, a passive master that can take over for the active master at any time, and a read-only replication slave (not shown) that we use for backups and analytics. Replication is configured so that the active master follows the passive master, the passive master follows the active master, and the analytics slave follows one of the masters. For the remainders of this post, I will refer to the active master as the master and the passive master as the standby. The benefits of this master-master configuration is that it allows us not only to failover from master to standby if the master becomes unhealthy, but also allows us to perform patching, reboots, lengthy migrations, and other kinds of database maintenance without impacting our users. Well, almost...
high availability mariadb master slave query db dbms backup replication failover painless administration configuration perform patch reboot application remain impact user configure maintain
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
Saved by uncleflo on February 8th, 2015.
A lot of people know us for our online toy production works, but we also make customize work. If you are an artist, or work for a company that needs to have a toy made for promotional events or any reasons, simply send us an email to support@patchtogether.com. Our minimal order start as low as 50 units for resin, 300 for plush and vinyl.
design toys patch together plastic create mould resin product process buy custom production quote community hardware construct
Saved by uncleflo on January 26th, 2012.
After a friend bought a RevoDrive3 120GB without doing much research, I got annoyed that there wasn't any Linux support, so I looked at the Windows driver and wrote in some Linux support. Written & tested remotely on his machine, in 6 hours on a Saturday afternoon. It _should_ work for RevoDrive3, RevoDrive X2 as well as zDrive R4, as they all seem to use the same Marvell 88SE9485 part and Sandforce 2281 or 2582 together. My patch has been submitted to the linux-kernel, linux-scsi, linux-ide mailing lists for review and inclusion. http://www.spinics.net/lists/linux-scsi/msg54932.html Anybody that wants to use it, you need to apply the linked/attached patch on top of a kernel at least v3.1-rc1 or newer.
linux development patch bios support revodrive zdrive marvell sandforce kernel scsi ubuntu
Saved by uncleflo on January 26th, 2012.
In the OCZ RevoDrive3/zDrive R4 series, the "OCZ SuperScale Storage Controller" with "Virtualized Controller Architecture 2.0" really seems to be a Marvell 88SE9485 part, with OCZ firmware/BIOS. Developed and tested on OCZ RevoDrive3 120GB [PCI 1b85:1021] Should work on: - OCZ RevoDrive3 (2x SandForce 2281) - OCZ RevoDrive3 X2 (4x SandForce 2281) - OCZ zDrive R4 CM84 (4x SandForce 2281) - OCZ zDrive R4 CM88 (8x SandForce 2281) - OCZ zDrive R4 RM84 (4x SandForce 2582) - OCZ zDrive R4 RM88 (8x SandForce 2582) All of this because a friend recently bought a OCZ RevoDrive3 and was bitten by the lack of Linux support.
linux compile support scsi revodrive zdrive ocz patch code development storage controller architecture marvell bios firmware
No further bookmarks found.