Explore >> Select a destination
|
You are here 
|
adam.younglogic.com | ||
| | | | |
seasidetesting.com
|
|
| | | | | In preparation of a workshop at Agile Testing Days 2022, I'm setting up a Raspberry Pi as a backup system for participants, to be prepared if things go wrong. Especially one of the first steps "Installing Ruby - If Necessary" has the potential to fail or take too long. With the keyboard configured (see the... | |
| | | | |
jinyuz.dev
|
|
| | | | | There was a pull request on GitHub and it contains a feature I wanted to test. I didn't know how to test it locally. Should I just copy the changes to my local since the changes weren't that big? But what if it was? Luckily, I found some answers by googling and decided to write it up for future reference. Git provides a command for it and here is the sample syntax | |
| | | | |
endot.org
|
|
| | | | | I've been using git_backup to back up the websites I run for quite a while now. It works well and I only need to scan the daily cron emails to see if the backup went well or if there were any odd files changed the day before. One thing that I didn't expect when I started using it was how it would enable developing those websites in a sandbox without any danger of affecting the production instances. | |
| | | | |
truss.works
|
|
| | | A git workflow that supports feature development isolation, continuous deployment, and has minimal overhead when performing common operations like branching and merging | ||
