Third-party backup vendors provide you with data protection solutions that significantly exceed the capabilities of backup scripts. Let’s show on the example of GitProtect backup and Disaster Recovery software for DevOps stack, how third-party backup tools can help organizations ensure data integrity, availability, and quick recovery in the event of failure. - Source: dev.to / over 1 year ago

Access-Control-Allow-Origin: https://gitprotect.io Access-Control-Allow-Methods: GET, POST, PUT, DELETE Access-Control-Allow-Headers: Content-Type, Authorization Access-Control-Allow-Credentials: true. - Source: dev.to / over 1 year ago

In the beginning of this blog post we said that security is a top priority in IT. Thus, it’s important to make sure that the source code is safe in any event of disaster. One of the best ways to do that is DevOps Backup with Disaster Recovery technology. While building your backup strategy, you should make sure that your backup follows the backup best practices, including the possibility to keep your backups in... - Source: dev.to / almost 2 years ago

Backup scripts are effective to an extent but for complete, automated and all-inclusive backups for GitHub (and other VCS), consider professional backup vendors, for best data protection. Check out solutions like GitProtect.io :)) https://gitprotect.io/. - Source: Hacker News / over 2 years ago

Unfortunately, we all know that we cannot avoid mistakes. Trial and error are curial in the development process of the product and engineering career. No matter how great programmers we are, we’ll slip up sometimes. The main question, therefore, is not if we make mistakes, but rather how well we can deal with them and fix the problems we are facing. Fortunately, Git offers a series of methods for undoing and... - Source: dev.to / over 2 years ago

There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: almost 5 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: almost 5 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: almost 5 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: almost 5 years ago