• 2 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: September 5th, 2024

help-circle


  • All the important login information should just be present somewhere in your home folder. If you back that up and restore it later you should be fine, no need to save the dropbox binary.

    If that is no option and you only want to back up dropbox files and nothing else follow the instructions below (I can’t guarantee that they will work, but they should):

    Back up the whole system, if something goes wrong you can at least restore to a working state. Read the instructions at least once completely before following them.

    Look at the documentation for dropbox to see which files are relevant and need backing up. Its the Dropbox folder with all the files, but will probably be some folders/files in your $HOME too, which store login information. Lets hope that they don’t store some metadata there that will invalidate the config if it’s running on a different machine (to prevent what you are trying to do).

    If there is no documentation, you can stop dropbox completely. Look for dropbox processes that don’t get stopped when you stop the GUI with something like pgrep -f -i dropbox.

    Once you are sure all dropbox processes are stopped run inotifywait -r -m ~. That command wont exit unless you stop it by issuing ^C. It will list all filesystem events in your home directory. Now start dropbox and see which files it accesses, those are the files you need to back up. It will probably be one or more whole directories in ~/.config and ~/.local.

    Add those files to a tar archive using something like this: tar cvJf dropbox_config.tar.xz [list of folders...]. Savre the resulting tar file somewhere else, reinstall and extract it using tar xvJf dropbox_config.tar.xz. Take care to run those commands from the same directory.

    The dropbox login secrets might also be stored in your system’s keyring, if you are using GNOME, then that will be GNOME Keyring. Open your system’s credential manager and look for stuff related to dropbox. Look for instructions on how to back up and restore those secets. I don’t use that often enough to be able to give you more detailed instructions right now though.

    References

    Edit:

    • backups
    • keyring








  • Hmm. The first section about cloud service providers is a bit weird to me. There are providers which “keep my best interests in mind” as part of their business model, backblaze would be one. Their whole idea is to provide a good backup services. Encrypting my data before transit also doesn’t make me worried that it will be accessed by them or any of their employees because they will only get some garbled mess.

    Compare that to google, another cloud service provider. Their business model is to make money by selling me ads (foremost), they do that by gathering as much data as possible. Here all my answers would be negative.

    This puts me in an awkward spot where I nearly every time answer with “Neither agree nor disagree”, because there is more to it and not because I don’t have an opinion.







  • redxef@feddit.orgtoLinux@lemmy.mlWhy do we hate SELinux?
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    9 months ago

    Docker container can’t read a bind mount. Permission issue? No, it’s SELinux, again. And I didn’t even install it explicitly, it just got pulled in by another package.

    And to be clear, the issue isn’t SELinux really, but unexpected non standard behaviour which I never asked for (never explicitly installed it).





  • Looks good, I use a lot of the stuff you plan to host.

    Don’t forget about enabling infrastructure. Nearly everything needs a database, so get that figured out early on. An LDAP server is also helpful, even though you can just use the file backend of Authelia. Decide if you want to enable access from outside and choose a suitable reverse proxy with a solution for certificates, if you did not already do that.

    Hosting Grafana on the same host as all other services will give you no benefit if the host goes offline. If you plan to monitor that too.

    I’d get the LDAP server, the database and the reverse proxy running first. Afterwards configure Authelia and and try to implement authentication for the first project. Gitea/Forgejo is a good first one, you can setup OIDC or Remote-User authentication with it. If you’ve got this down, the other projects are a breeze to set up.

    Best of luck with your migration.