#dev | Logs for 2024-11-22

« return
[09:09:59] <devbot> [infrastructure] 14ennwise pushed 1 commit to branch 03master: https://github.com
[09:09:59] <devbot> • 14ennwise (03e236a2d2): "🍺 Homer's not the only plow king! Added MrPlow to our IRC, where #fite RPG action takes the stage. Because if you're going to combat with humor,…
[09:11:49] <janrinok> o/ - you are up late!
[09:13:32] <kolie> howdy.
[09:18:40] <janrinok> I remember '#fite'!
[09:20:27] <kolie> I guess I revived it lol.
[09:21:11] <janrinok> There used to be fites breaking out in various channels :)
[09:21:32] <janrinok> or at least the results of fites...
[09:21:58] <devbot> [infrastructure] 14ennwise pushed 1 commit to branch 03master: https://github.com
[09:21:58] <devbot> • 14ennwise (031eb67a63): - Implement persistent storage for player data using a JSON file.…
[09:28:56] <devbot> [infrastructure] 14ennwise pushed 1 commit to branch 03master: https://github.com
[09:28:56] <devbot> • 14ennwise (0367e83793): Refactor IRC bot to clean nicknames before adding players
[09:53:52] -!- Loggie [Loggie!Loggie@Soylent/BotArmy] has joined #dev
[10:05:07] <devbot> [infrastructure] 14ennwise pushed 1 commit to branch 03master: https://github.com
[10:05:07] <devbot> • 14ennwise (03d155d1bf): Add effectiveness pools for combat and implement reset command for staff members
[22:48:42] -!- Fnord666_ [Fnord666_!~Fnord666@fd0f:9ae5:zysp::r] has joined #dev
[22:48:43] -!- Fnord666_ has quit [Changing host]
[22:48:43] -!- Fnord666_ [Fnord666_!~Fnord666@Soylent/Staff/Editor/Fnord666] has joined #dev
[22:49:46] Fnord666_ is now known as Fnord666
[22:53:25] <kolie> https://github.com
[22:53:26] <systemd> ^ 03GitHub - SoylentNews/infrastructure
[22:53:38] <kolie> That is the main system as of yesterday.
[22:53:51] <kolie> There are mods to dev and some irc bots that are meaningless.
[22:53:57] <kolie> I'll commit them but they aren't in yet.
[22:54:17] <kolie> Fnord666 ^^
[22:54:30] <Fnord666> It's going to take me a while to get through the README.md anyway. :)
[22:54:32] <kolie> If you check that out, you can test anything or everything in part or whole.
[22:54:38] <kolie> no readme lol
[22:54:40] <kolie> u needme
[22:55:07] <kolie> its pretty easy but yea no docs really rn
[22:55:28] <kolie> What you will want to do, is create a user called devops, uid/gid 50000
[22:55:32] <kolie> And do everything under that user.
[22:55:54] <Fnord666> :) You've done a hell of a job on this and I know everyone appreciates it. Thank you.
[22:56:12] <kolie> no worries man, glad to help and I appreciate the gratitude.
[22:56:39] <Fnord666> We definitely would not be where we are today without you and might even not be anywhere at all.
[22:58:04] <kolie> You guys would've figured out something. I like to think this was the quickest route with no changes.
[22:58:18] <kolie> I'm glad its here and its all worked out so smooth.
[22:58:32] <kolie> to another decade of existing.
[22:58:58] <Fnord666> cheers!
[23:09:37] <kolie> The process Fnord666, once you have a uid 50000/gid 50000 user is to setup the environment.
[23:09:53] <kolie> there is a script in /utils that puts some commands in the path of the current user.
[23:10:03] <kolie> ull want to do that in the devops user
[23:10:09] <kolie> also instlal docker, make sure devops user can use docker.
[23:10:32] <kolie> Once that's squared away, its a matter of deciding what services you want to setup.
[23:11:15] <kolie> config is pulled from /secrets/environment/servicename.env and /secrets/environment.env ( environment being devleopment or production right now ) you can use whatever. a local .env file in a service directory overrides everything.
[23:11:49] <kolie> Everything else in a folder /opt/servicename usually, but check the docker-compose for the service for specifics on what it needs.
[23:12:04] <kolie> dc up, dc down in a folder
[23:12:21] <kolie> alias dc='compose.sh'
[23:12:47] <kolie> dc up servicename [args] for only doing an individual service from the docker container.
[23:13:06] <kolie> use dc up down because thats what handles the environment variables and the pre and post hooks etc.
[23:13:58] <kolie> theres templating for loading secrets, any file in the folder with name.template, gets .template stripped and environment variables replace in it, pre-hook runs before this happens, post-hook runs after
[23:14:41] <kolie> the idea is, pre-hook may generate some stuff, secrets get filled in, post hook runs to remove the secret filled file from the dev directory to /opt or wherever it needs to be, and then the container is ran with the proper environment variables using compose.
[23:15:21] <kolie> We can backup all the secrets cause we store them all in one location /secrets, persistent data is all in /opt, everything that can be commited, configs but not secrets is in infrastructure
[23:28:46] <Fnord666> Thanks! I'll have to try it out this weekend.
[23:28:58] <kolie> I wont be around till monday, gl