Post AdbzXIAveP4ctXCEQi by Maholmire@annihilation.social
(DIR) More posts by Maholmire@annihilation.social
(DIR) Post #Adbo1Z68tkM7CT0Spc by mint@ryona.agency
2024-01-07T16:59:18.651585Z
2 likes, 0 repeats
@pwm @Maholmire @dcc @i @p @emma Using connection with CGNAT is like paying to peep through keyhole at the brothel.
(DIR) Post #AdbofekTJE9uJ9zGCG by mint@ryona.agency
2024-01-07T17:06:45.709212Z
2 likes, 0 repeats
@Maholmire @dcc @pwm @i @p @emma >email serverJumping right into the volcano pit. I'd say start with a basic static site and work your way from there.
(DIR) Post #AdbpFEDnPgmuSdfJXE by i@declin.eu
2024-01-07T17:13:13.422265Z
2 likes, 0 repeats
@mint @Maholmire @dcc @pwm @p @emma in the spirit of bothering to pick nixos, it's a single config entry, https://nixos-mailserver.readthedocs.io/en/latest/setup-guide.html
(DIR) Post #AdbpfMJ7yLd14IcRl2 by p@freespeechextremist.com
2024-01-07T17:17:58.306796Z
0 likes, 0 repeats
@Maholmire @dcc @emma @i @mint @pwm > Would you recommend keeping each service isolated within their own containerOnly if your goal is "learn about containers" instead of "operate functional service". There is no other reason to do that. Walk before you run.Once you have a basic thing working, then maybe try splitting things into containers. For basically any system on fedi, you don't actually need that. User separation works fine.FSE lives on a VM, the associated services all live on the same VM, except Postgres, which lives on the host machine, and more for I/O performance than because it matters too much to split the stuff up. (Initially, Postgres had to be put onto another machine when FSE was still on Frantech, but this was because the available disk space had been maxed out.)
(DIR) Post #AdbppVz2qrtnyS4IvA by p@freespeechextremist.com
2024-01-07T17:19:48.448855Z
0 likes, 0 repeats
@Maholmire @dcc @emma @i @mint @pwm Install prerequisites, install software, turn software on.
(DIR) Post #AdbqJHXD8YUlqhF8pE by p@freespeechextremist.com
2024-01-07T17:25:11.227922Z
0 likes, 0 repeats
@Maholmire @dcc @emma @i @mint @pwm > all of that information can be a bit much to take in at times.All the more reason to simplify it until it is digestible. "The dog chews on the bone because he can't swallow it." Do one thing at a time: set up a system. Install something. Run it. Make it run reliably. Set up a second thing.
(DIR) Post #AdbqZbg40wtCxDAV7o by p@freespeechextremist.com
2024-01-07T17:28:08.248797Z
1 likes, 0 repeats
@Maholmire @dcc @emma @i @mint @pwm It's not as bad as people say, but it is a little obtuse sometimes and it is worth doing, I think. It does paint a target on your machine's back, though, so make sure you know how to tell when something bad is happening before you jump in.mint is right, just set up a web server first.
(DIR) Post #AdbzOFs6qVHH905ILg by p@freespeechextremist.com
2024-01-07T19:06:55.844152Z
2 likes, 0 repeats
@Maholmire @dcc @emma @i @mint @pwm Most people use nginx. I think nginx is fine; I like lighttpd. If it's just a static site, you won't notice much difference between the two.If you're just learning, you might try lighttpd because it supports CGI scripts and CGI scripts are probably the simplest way to do very basic web stuff. (People shit on CGI, but this is superstitious and they do not know what they are talking about and have never written a CGI script. https://git.kernel.org/ uses cgit, which is CGI.) There's also mod_magnet, which lets you embed little Lua programs instead of CGI or reverse-proxying to an upstream server. I like lighttpd.nginx is so popular that 99% of the tooling you find and 99% of the documentation you will find is written for nginx. nginx is fast and reliable and nice. Unless you know off the top of your head the difference between the various FD polling mechanisms, everything anyone says about scaling will not apply, they've never had to scale anything anyway, etc.. etc. Bottom line is nginx is easy to work with and everyone you talk to will be able to help.Apache used to be 90% of the web. It's older, it's a little balkier, it's a pain to configure, but it's another option. Notably, while all of these webservers are missing one thing or another, Apache supports basically everything. You will have a difficult time finding something that no one has added Apache support for.thttpd is probably the easiest one to get up and running. `thttpd -p 8080 -d .` serves up the current working directory on port 8080. (thttpd is kinda fascist about file permissions but other than that it is the quickest way to go from "no webserver" to "webserver is up and running and serving files".) It does CGI, it doesn't do reverse-proxying.There are about a million webservers. I think (don't quote me on this) that if you install 9base, rc-httpd will work on Linux under inetd. busybox comes with a webserver. The reason HTTP took off is, in part, that it was extremely easy to implement, so there's no shortage.Anyway, just use nginx.
(DIR) Post #AdbzXIAveP4ctXCEQi by Maholmire@annihilation.social
2024-01-07T19:08:32.412235Z
0 likes, 0 repeats
I'll probably experiment with a couple solutions throughout next week. @p @dcc @pwm @i @emma @mint
(DIR) Post #AdbzZqBQBHLewodr8K by waltercool@pl.slash.cl
2024-01-07T19:08:58.696993Z
1 likes, 0 repeats
@p @Maholmire @dcc @pwm @i @emma @mint Nginx have some benefits tho, like cache system, load balancer and kinda flexible rewrite rules.
(DIR) Post #Adc10bU92H6z8Sj0pE by i@declin.eu
2024-01-07T19:25:02.564079Z
1 likes, 0 repeats
@Maholmire @dcc @pwm @p @emma @mint also consider not doing any of that with NixOS, and try virtualizing https://dietpi.com/ insteadit's still features an abstract software manager: https://dietpi.com/docs/software/and most guides online will tell you what you can do to make things work on debian yourself
(DIR) Post #Adc1Q6WykHmUf5D6Ey by p@freespeechextremist.com
2024-01-07T19:29:40.484658Z
0 likes, 0 repeats
@Maholmire @dcc @emma @i @mint @pwm Well, I'm not helpful for NixOS debugging because I don't use NixOS.
(DIR) Post #Adc1bJ1SdsWiaaoF6W by p@freespeechextremist.com
2024-01-07T19:31:41.957602Z
2 likes, 0 repeats
@waltercool @Maholmire @dcc @emma @i @mint @pwm Yeah, but Apache and lighttpd have cache systems, load-balancing, and flexible rewrite rules.
(DIR) Post #Adc27FJJyjIKLMOSps by p@freespeechextremist.com
2024-01-07T19:37:28.315316Z
0 likes, 0 repeats
@i @Maholmire @dcc @emma @mint @pwm > also consider not doing any of that with NixOS,Careful, it'll turn into a distro-arguing thread and there is no coming back from that.
(DIR) Post #Adc2x02bzlf02oFvoO by p@freespeechextremist.com
2024-01-07T19:46:49.506362Z
1 likes, 0 repeats
@Maholmire @dcc @emma @i @mint @pwm > That said, the reason I did decide to use it is because of its reproducibility."I can make the program run as fast as you want, provided it doesn't have to print the correct answer." You want to make sure that you have prioritized the correct thing.There's a rule of thumb when writing library code: do it manually at least three times before you try to write a library that does it. The reason for this rule of thumb is that it forces you to learn the pain points before trying to generalize and to get a good grasp of the space you're working in. Have you had problems with reproducibility in the past? I'm going to go out on a limb and say that since you are setting up your first webserver, you have not. Solving problems that don't exist is going to impede progress.I'd worry about getting one webserver running before worrying about avoiding the process of reproducing it. Ansible is more reproducible than you need at the moment, and no one's recommending Ansible because you don't need Ansible. You definitely don't need NixOS.