(untitled)

I've finally gotten a domain, and I have downloaded lainchan. github.com/lainchan/lainchan How do I get the code into it, now?

>>11555 Look at the requirements, recommendations, and installation sections of the README. Use the beginners questions thread next time.

>>11555 Are you by any chance trying to reanimate a recently deceased image board which died in mysterious circumstances?

>>11555 A thread died for this

VPS, apache, upload code to VPS, associate VPS with domain

>>11557 >mysterious circumstances you know good and well what those were, lmao

This thread feels like it fell from /g/

>>11556 >Download and extract lainchan to your web directory What is a web directory?

>>11562 do you have a working webserver ? Do you have a server upon which to host the site ? do you know what these words mean ? do you know what a firewall is or what it does ? what about portforwarding ? You likely want to rent a server from somewhere, this will be easy. then follow i.e. a digital ocean tutorial for setting up a webserver, apache or ngnix, and have it run php. You'll tell the registrar the IP address of this server so it can point the domain there. If you want to run it from your home, you'll need to see how your ISP has things setup and configure your router. A rental server will be quicker and easier but costs a bit (often ~5usd/mo).

>>11563 I don't know much about technology, but I think a webserver is a computer that hosts the website, but you've implied these are two different things. I think a firewall is what protects it from attacks, and I don't know what portforwarding is. I didn't know that a server only cost 5usd/mo, that makes me happy.

>>11564 Well, you need a sever, and then you need the software on it that handles the website, which is unfortunately also called a server. Lainchan uses the webserver called nginx so you probably should, too. In this case you also want a database for the server to use. Digital ocean has some very hand holding tutorials about this type of thing, such as : https://www.digitalocean.com/community/tutorials/how-to-install-linux-nginx-mysql-php-lemp-stack-ubuntu-18-04 obviously not for lainchan specifically but it will get you most of the way there. After this is all setup you'll need to install lainchan into the web directory, which should be easy but I've never done it so idk but lets see once you get there. are you running this on a machine you own or going to get a rental server? If the former you probably first want to install a linux distro such as debian.

>>11557 >>11560 I hope we're talking about THAT board.

>>11566 I at least was, but I am not op. Also are you aware of the bunker?

>>11567 As a cafe netizen and latefren, yes, I am.

>>11565 Why not Linux Mint? What do people in the know even think about that distro?

>>11569 linux mint's perfectly OK and would work for this task, but its mostly meant as a desktop system as opposed to a server system. That digital ocean tutorial should likely work for linux mint, ubuntu, or just about any other debian based distro. For setting up a server like this running a graphical interface probably won't make anything much easier, but it won't make it any harder either if your machine isnt super constrained. For most purposes debian, ubuntu, and mint are nearly interchangeable.

>>11569 >>11570 >Linux Mint? Linux Mint is not a server OS. Do not use regular Ubuntu, Linux Mint or Arch for a server. Instead, want a secure and stable OS for your server. Ubuntu Server (sic!) or Debian/Devuan stable is the way to go. Linux Mint comes with a ton of stuff that shouldn't be there on a server (like Xorg+DE). More stuff = bigger attack surface. You should install and configure OpenSSH server (pro tip: also install tmux on your server and launch it after you SSH into it. This way your processes won't get killed if you lose connection). Prefer SSH keys over using a password. Forbid root login. >https://wiki.archlinux.org/title/Openssh If you don't have much experience with the command line, you can read this free book: https://linuxcommand.org/tlcl.php When you encounter problems, check out the relevant page from ArchWiki (even if you don't use Arch/Artix) but do not forget to read your distro's documentation as well.

>>11571 Official Arch repos features arch-audit its only purpose is to scan your packages for anything vulnerable. I promise you for ever 10 packages that come up, 9 aren't needed to run a server

I think we should remember that OP really is very new, doesn't know what half of these things mean, doesn't have any associations that we all do with arch/debian/et cetera. Does he even want to learn linux or just get a chan running ? Can we all just agree with some basic suggestion like Debian Stable ? I know the systemdtards are gonna hate it but its pretty darned normal and has a lot of documentation that will just work for it.

>>11573 fair dude. just use debian stable. it works and systemd isn't satan. at most it's one of those hell duke dudes no one remembers except goths.

1 install ubuntu server 2 install apache, mysql, php, and all the required packages listed in the readme 3 host your lainchan directory with apache and perform mysql_secure_installation 4 configuration hell 5 using your router and domain provider, direct your url to your server

>>11575 Thank you! This may be a dumb question, but if I need to download this to my computer, if I have my computer sleep or shut down, will it make my website temporarily go offline?

>>11576 if you run your website off your computer, then yes when your computer is turned off, the website will be off, too.

>>11576 i don't recommend hosting an imageboard on your computer for liability reasons, unless you can at least mask it with a reverse proxy

>>11578 >>11577 Those guys just reccomended me to download a web server to host it off of my computer! I'm so confused now.

>>11579 I think a lot of people on here keep their computers or at least one computer running all the time. This is largely a computer nerd chan so thats not too weird. There's a couple options you could consider, like renting a Vps, running your computer all or nearly all the time, or getting like a little cheap computer like an orange pie or raspberry pi and running a server off that.

>>11578 To clarify, "liability reasons" means that when you're thinking about hosting a web site for random strangers to come and post things that you can only effectively moderate after the fact, there are essentially two paths to choose from: 1. Host the website from your home on your own computer equipment. The person for everyone to contact when someone hijacks a vulnerable service on your home server and starts sending out spam emails and DDoS attacks is you. When someone posts federal prison no-no pictures on your website, the thing standing between the police and you is your ISP, and by "standing between" I mean that they promptly furnish the police with your address upon informal request. Nothing else is being hosted from your home except your own website, so it tends to stand out. You have no relationship established with the cybercrime units in your jurisdiction. Your house gets raided and your computer equipment gets seized indefinitely. 2. Host the website on someone else's equipment in a data center (note: this can be done for a fraction of the monthly cost of a static IP address from most ISPs (no, nobody will take your DynDNS website seriously)). When someone hacks your soykaf and uses it to attack other stuff on the internet, your server host gets contacted about it instead of you. When someone posts spicy media on your site, your server host stands between you and the police. You choose what that means when you choose the server host. Maybe the host doesn't even know who you are. Maybe they do but they don't provide any customer information to the authorities without a proper warrant. Maybe something in between. The host owns the computer equipment and deals with the fallout when people use it to do bad things. They have relationships with law enforcement. Law enforcement knows what business they're in, so they don't constantly get raided as long as they duly address abuse of their services. If you turn out to be bad at moderating your website and you keep making them deal with it, they might kick you off their service, but you don't get all your personal electronics torn apart. Note that both options require some degree of effort and involve a high probability of stress; neither option involves being able to "fire and forget" or "let it run itself" in any way -- or, as they say, you can try.

>>11581 Thank you so much! I will go for the second option!

>>11581 do you have any recommendations for linux server hosts?

vultr seems okay, haven't used them though.

>>11583 Yeah I guess but it's basically just a list of ones I've used lol They aren't tailored for anoymity or security or cyberpunk cred or whatever. In a nutshell the list would be "just browse lowendbox.com" + "I know AWS isn't very 'punk' and yes Oracle is gross but they have a lot of decent free soykaf to take advantage of" Servarica (check out "unlimited storage") I'm running a free-for-a-year VPS on atlantic.net that I'm pretty sure should have expired a few months ago, it's pretty neat and supports arch btw When I had a dedi I used SoYouStart / Kimsufi, not terrible

>>11559 Ok, I'm still stuck on >VPS which one do I choose?