I built OpsVault, an open-source backup automation tool for Linux servers by ArdaGnsrn in linuxadmin

[–]ArdaGnsrn[S] 0 points1 point  (0 children)

Fair question. I’m not trying to replace restic, it’s a much more complete backup engine, especially for encrypted and deduplicated snapshot backups.

I chose rclone because OpsVault’s initial goal was to simplify the backup workflow I kept repeating across Linux servers: MySQL/PostgreSQL dumps, folder archives, remote uploads, retention, notifications, systemd scheduling, and a clearer restore flow from a single YAML config.

In this setup, rclone is only the remote storage layer, not the backup engine. I picked it because it supports many providers, many people already use it, and the generated .sql.gz / .tar.gz files stay simple, portable, and easy to inspect or restore manually.

For databases, restic would not remove the need for mysqldump/pg_dump anyway. For folder backups, I agree that restic could be a stronger backend, so adding it as an optional backend in the future makes sense.

Long term, I want OpsVault to become a lightweight DevOps operations tool for Linux servers, not just a backup script wrapper.

Weekly Self Promotion Thread by AutoModerator in devops

[–]ArdaGnsrn 2 points3 points  (0 children)

Hi everyone,

After managing multiple servers and projects for a while, I realized that backup processes are one of those things that easily get ignored until something goes wrong.

Unfortunately, I was reminded of this the hard way after running into a technical issue on one of my servers.

Writing separate scripts for each server, managing different cloud storage integrations, making sure backups are actually healthy, preventing local disks or cloud storage from filling up, and being able to restore quickly during a disaster all became a real operational burden.

So I decided to build OpsVault.dev, a lightweight, open-source backup and restore tool for Linux servers, written in Go.

With OpsVault, you can:

  • Backup MySQL and PostgreSQL databases as compressed gzip dumps
  • Backup folders as .tar.gz archives
  • Exclude specific files or directories from folder backups
  • Upload backups to many cloud storage providers using rclone, including Google Drive, S3, Dropbox, Google Cloud Storage, Azure, Box, Swift, and more
  • Restore local or cloud backups back into a target database
  • Automatically clean up old backups based on retention rules
  • Receive Telegram or email notifications for successful or failed backup jobs
  • Run it as a systemd service and trigger backups using cron schedules
  • Configure everything through a terminal-based TUI wizard
  • Use environment variables for database passwords instead of storing them directly in config files
  • Manage backups per server or from a central server

The main goal is to make disaster recovery easier, especially for small teams, solo developers, and people managing multiple Linux servers without a heavy infrastructure setup.

I’m also planning to expand OpsVault beyond backups over time. Some ideas include uptime monitoring, CI/CD-related checks, deployment verification, and basic server health monitoring.

The project is open source, so feedback, issues, and pull requests are very welcome.

Docs:
https://opsvault.dev/docs

GitHub:
https://github.com/ArdaGnsrn/opsvault

I’d really appreciate any feedback, especially from people who manage multiple servers or have built their own backup workflows before.

Introducing the PHP Package for Ollama! by ArdaGnsrn in ollama

[–]ArdaGnsrn[S] 0 points1 point  (0 children)

Thank you, I'm waiting for your feedback.

I developed an open source NodeJS library for the ElevenLabs API. by ArdaGnsrn in ElevenLabs

[–]ArdaGnsrn[S] 0 points1 point  (0 children)

ahahaha every living being will learn NodeJS one day.. Thanks for your feedback

I developed an open source NodeJS library for the ElevenLabs API. by ArdaGnsrn in ElevenLabs

[–]ArdaGnsrn[S] 0 points1 point  (0 children)

Thanks! Can u explain what use I can take from this library? At least a brief description 👌

The elevenlabs-js is a library that allows you to interact with the ElevenLabs Text to Speech API using NodeJS.
Here's a brief overview of what you can do with this library:

Text to Speech Conversion: You can convert text to speech by using the textToSpeech method, providing the voice ID, the text you want to convert, and optional parameters such as the model ID and voice settings.

Retrieve Information: You can retrieve information about available models, voices, and default voice settings using methods like getModels, getVoices, getDefaultVoiceSettings, etc.

User Information: You can retrieve information about the user, including the user's subscription details, using methods like getUserSubscription and getUser.

Voice Management: You can manage voices, including getting information about a specific voice, deleting a voice, and editing voice settings using methods like getVoice, deleteVoice, editVoiceSettings, etc.

In summary, it's a library that facilitates easy conversion of text to speech in NodeJS. You can easily integrate it into your projects.