• 1 Post
  • 64 Comments
Joined 8 months ago
cake
Cake day: July 14th, 2024

help-circle





  • This is something that doesn’t really need to be self hosted unless you’re wanting the experience. You just need:

    1. Static website builder. I use hugo but there’s a few others like jekyll, astro
    2. Use a git forge (github, gitlab, codeberg).
    3. Use your forges Pages feature, there’s also cloudflare pages. Stay away from netlify imo. Each of these you can set up to use your own domain

    So for my website i just write new content, push to my forge, and then a pipeline builds and releases the update on my website.

    Where self hosting comes into play is that it could make some things with static websites easier, like some comment systems, contact forms, etc. But you can still do all of this without self hosting. Comments can be handled through git issues (utteranc.es) and for a contact form i use ‘hero tofu’ free tier. In the end i don’t have to worry about opening access to my ports and can still have a static website with a contact form. All for free outside of cost of domain.


  • Im not familiar with doku wiki but here’s a few thoughts

    • privacy policy is good to have regardless of what you do with rest of my comments
    • your site is creating a cookie “dokuwiki” for user tracking.
    • cookie is created regardless of user agreement, rather than waiting for acceptance (implied or explicit agreement). As in i visit the page, i click nothing and i already have the dokuwiki cookie.
    • i like umami analytics for a cookieless google analytics alternative. They have a generous free cloud option for hobby users and umami is also self hostable. Then you can get rid of any banner.




    1. Site wasn’t properly reflexive for mobile
    2. If this is a portfolio then i would remove a lot of stuff like “watch list” and “current obsession”. The focus should be on your work and future projects
    3. Notes are ok for a start but can be improved. I think a “posts” or “blog” would be better section title, and the content should try to teach something you’ve learned rather than be the notes you took for a subject. The difference is that teaching reinforces your understanding of the topic. So pick something smaller from those topics and teach it. I wouldn’t redo your current notes necessarily, but going forward i would pick a more focused topic and teach.
    4. i would then move the “blog” or “posts” to your front page to show the most recent content and then link to /posts where the rest of it can be found. Or highlight projects on front page instead depending on what you want focus to be.
    5. move your front page content to a more “resume” section that includes a section for the tools you know. And still think about the length/space of this page. Like a printed resume, too long is bad. So make sure it outlines things nicely

    Overall if it was just a personal site id say its ok. But as a portfolio site you have some work to make it align with your goals. Good luck!






  • I assume Yale isn’t broke but idk. Universities are just like any other business where they will cut products that aren’t making money or performing as well as others. The article talks about the course needing many teacher assistants to field student questions and hold labs, and that originally these costs were covered by a donation which has now run out.

    It also could just be some internal politics and blaming it on financials is the public reason.

    But you’re not wrong that student tuition costs should theoretically go to the courses they sign up for




  • The archinstaller script is pretty good if you’re just needing a basic setup. Ive been really happy with a btrfs partion from the recommended disk layout, then using btrfs snapshots + grub bootloader to load from snapshots. You can also create a hook on pacman so that you create a snapshot when you upgrade packages.

    Since you didn’t mention your experience, id recommend looking at the various desktop environments so you know which one to pick during install. You can ofc change later.

    And read the arch docs. They are very good and have a lot of time invested into them. If you find you don’t have the patience to read them then you’re probably going to want to look at a different OS. Good luck!


  • Edit: i see now they’re talking about private IP, but in case you want to learn about getting a static IP for other things…

    Many ISPs will give you a dynamic (changing) IP rather than a static (unchanging) IP. Just check your IP once a week for a few weeks to see if it changes.

    There are some services that get around this by checking your ip regularly and updating their records automatically. This is called a dynamic DNS provider (DDNS). I used to use “noip” but since then there are quite a few like cloudflare DDNS.

    Beyond that you just would want to make sure your router or whatever device is assigning IPs on your network to give a static assignment to the server. Assigning IPs is handled by a DHCP server and it would usually be your router, but if you have a pihole you might be using that as a DHCP server instead.

    Between DDNS and DHCP you can make sure both your external IP and internal IP are static.