JSE's Blog

I'm still a scrub but finally got to 3000pp...

I'll either:

• a.) Be stuck at this rank forever
• b.) Look back on this blog post and LOL at how bad I was then.

Who am I kidding? It'll probably be a.

I couldn't upload images to htmly with my lighttpd config. Further, the lighttpd config blocked my favicon.ico file. All images would result in a 404 when uploaded, despite ls-ing to the directory shows it uploaded successfully. I'm not using vhost with lighttpd... and honestly ... I blindly copied and pasted the config directly from the htmly documentation found on the github readme (and of course... enabled the rewrite mod in lighttpd.conf which is as simple as uncommenting. The verbatim code was:

$HTTP["url"] =~ "^/config" {
  url.access-deny = ( "" )
}
$HTTP["url"] =~ "^/system/includes" {
  url.access-deny = ( "" )
}
$HTTP["url"] =~ "^/system/admin/views" {
  url.access-deny = ( "" )
}

url.rewrite-once = (
  "^/(themes|system|vendor)/(.*)" => "$0",
  "^/(.*\.php)" => "$0",

  # Everything else is handles by htmly
  "^/(.*)$" => "/index.php/$1"
)

My issue was I would get 404s on images I upload. So I modified the line "^/(themes|system|vendor)/(.*)" => "$0", to show "^/(themes|system|backup|vendor|content/images)/(.*)" => "$0", since content/images is where the images reside when you upload them with htmly. Additionally, backup was added so you can download backups direct from the interface.

Next, I added a line directly below it "^/(favicon\.ico|robots\.txt|humans\.txt|sitemap\.xml)$" => "$0", which of course, ensures favicon.ico, robots.txt, humans.txt and sitemap.xml actually works.

It works. It's not perfect. I want to be able to create other directories without rewrite screwing me over for hosting random files and whatever else I feel like. Perhaps I'll setup proper vhosts and elaborate on that down the road as I work on this site. For now the config is in /etc/lighttpd/lighttpd.conf at the bottom, and it gets the job done, so I'm happy.

FWIW... here is my entire config I ended up modifying to for those of you who also want to blindly copy and paste :P

$HTTP["url"] =~ "^/config" {
  url.access-deny = ( "" )
}
$HTTP["url"] =~ "^/system/includes" {
  url.access-deny = ( "" )
}
$HTTP["url"] =~ "^/system/admin/views" {
  url.access-deny = ( "" )
}

url.rewrite-once = (
  "^/(themes|system|backup|vendor|content/images)/(.*)" => "$0",
  "^/(favicon\.ico|robots\.txt|humans\.txt|sitemap\.xml)$" => "$0",
  "^/(.*\.php)" => "$0",

  # Everything else is handles by htmly
  "^/(.*)$" => "/index.php/$1"
)

But yeah.... fixes that issue for you lighttpd users out there who can't upload images with the htmly platform :)

Why am I using lighttpd? Well certainly apache is out of the picture for a 128MB Low End Box. Lighttpd was the choice mainly because I've used it more than nginx. I like nginx and have used it a bit but lighttpd gets the job done for me where I have more experience with it (it use to serve the chickentalk.org forums I used to run a few years ago well so you can say I used it in "production") and is rock stable as far as I can tell for all the memory leak complaining I've heard about in the past, so I use it.

Perhaps one day I'll switch to nginx since that's where the community is at, but old habits die hard. It's always been my goto apache alternative.

So there's lots of tutorials on the osu!forums like "Ultimate guide to low-latency osu! on Linux", "Solution: Running osu! In Ubuntu or Xubuntu", etc. And I'm sure these are all good tutorials that are awfully verbose. But I'm lazy and I didn't read them. I don't like reading too much, only writing, that's why I never proof read haha! I'm contrarian, it shouldn't be hard.

So here's the lazy way. I assume you know your way around linux and you actually know how to configure it (eg. Install proprietary graphics when needed) which personally, I feel that is beyond the scope of any one tutorial, especially how that changes so much and distros vary anyhow. Hardware configurations are a separate issue and effect far more than just osu! anyway, so look for tutorials on that if you need help with tuning any of your hardware (tablets, graphics, what-have-you). Google is your friend.

So if you are looking to install osu!... here is the TL;DR version

1. Install Wine. (If you're on Ubuntu or debian, it's as easy as an apt-get)
2. Create a 32bit prefix if you are on 64bit linux (you probably are). Don't know how? If you're learning to use linux and wine you should learn as pretty much everything you'll use in wine will need a 32bit prefix. A google search returns this for example.
3. Install .net 4.0 and some fonts. I don't know what fonts are necessary but winetricks makes life easy and has the option to install all fonts. Which, by the way... you should use winetricks to do both since it makes it really easy. Another easy apt-get on Ubuntu/Debian. Soooo if you're new.... to run Winetricks on your 32bit prefix? WINEPREFIX=/whatever/your/path/to/32bit/prefix winetricks
4. Finally, download osu! installer like you normally would on Windows. Fire up a terminal, cd to the directory where the installer is and run it in your prefix. Protip: Something like WINEPREFIX=/whatever wine osu\!installer.exe (Remember to escape the ! with a \ so Bash doesn't freak out over syntax crap)

It will install. I literally had no issues with getting it to work. No input lag. Great fps. I don't see the need, at least with the distro I was running (Ubuntu 16.10 at the time) to do any fancy hacking or installing different kernels. It works out of the box. You can then run the game osu\!.exe the same way you did with the installer. If you don't like using the terminal to launch it all the time make a launcher script or something on your favorite desktop environment of your choice to do it for you.

Otherwise if you want more help post a comment, post in one of the threads above, follow the instructions in those linked threads, cry to peppy to release the native linux client. But just don't make life too hard for you when you don't need to ;)