soo,, we have set up a web thingy that is intended to be used only locally.
-
soo,, we have set up a web thingy that is intended to be used only locally. it uses some open source software (gotosocial and enafore (with some light code patches)), some external scripts, and of course custom config files.
it's a quite marvellous piece of bespoke software, which we enjoy a lot. so we'd like to share the joy with others that might also make use of it
the question: we've heard of tools that make reproducing installations of software easier. we've heard about things like Docker, Nix, Ansible, etc., but they all look rather complicated. is there some gay piece of software that could help us with this, without forcing us to learn arcane sysadmin stuff?
i guess in the worst case we could just make a bunch of bash scripts + SystemD unit files. maybe a good place to start with, but there ought to be better (and still relatively lightweight) solutions

boosts ok, if gay

-
soo,, we have set up a web thingy that is intended to be used only locally. it uses some open source software (gotosocial and enafore (with some light code patches)), some external scripts, and of course custom config files.
it's a quite marvellous piece of bespoke software, which we enjoy a lot. so we'd like to share the joy with others that might also make use of it
the question: we've heard of tools that make reproducing installations of software easier. we've heard about things like Docker, Nix, Ansible, etc., but they all look rather complicated. is there some gay piece of software that could help us with this, without forcing us to learn arcane sysadmin stuff?
i guess in the worst case we could just make a bunch of bash scripts + SystemD unit files. maybe a good place to start with, but there ought to be better (and still relatively lightweight) solutions

boosts ok, if gay

update: it has decided to use technology that we are already familiar with:
- Firefox Multi Account Containers, to log into multiple instances of the frontend (a custom fork of Enafore).
- A SystemD unit file for the frontend.
- pacman/PGKBUILD for packaging the frontend.
- A git repo with further config files and a readable Markdown file documenting how to install the packages and config files.
- The documentation will also contain a section about how to create accounts, and how to import emojis (with an existing script).
- The documentation should also explain how to make backups. There already exist backup scripts for GoToSocial, but we haven't tried them out yet (so far we only made manual backups).It made a plan, and is already done with the first step.

-
R relay@relay.infosec.exchange shared this topic