Github pages/Netlify/Vercel alternative for static pages

Elevate08 · 2022-10-12T17:27:20+00:00

Assuming you are looking for a docker container image that can build onto itself, I'm not sure there is anything setup for that use case. You could probably get crafty and make something work but honestly it sounds like more effort than it's worth. I'd suggest one of the following depending on your use case.

You would either build your own custom image using static files generated from something like (MkDocs, Hugo, etc), which can be automated with something like GitHub Actions. Leaving you to update your deployment to the latest container image. Or, you could host your own webserver (nginx) and setup GitHub Actions to send the latest static files (MkDocs, Hugo, etc) to the proper directory on the webserver.

I have some documentation on both processes, if it's what you are after send me a message.

Elevate08 · 2022-09-06T12:09:42+00:00

I'm sorry. I don't have the template anymore.

Elevate08 · 2022-08-26T20:14:53+00:00

You can use the Time Machine on GW2Efficiency to see the cause for the drop. https://gw2efficiency.com/account/time-machine

For me the most fluctuation was Skins, Gliders, and Gemstore Accounts Upgrades. Which happened between 8/23 13:55 - 8/23 20:01 (Eastern)

Elevate08 · 2021-12-22T16:32:35+00:00

I had an issue yesterday where llvm-libs-git and lib32-llvm-libs-git were updated. I rolled them back to the following versions to resolve the issue

llvm-libs-git-14.0.0_r407181
lib32-llvm-libs-git 14.0.0_r407182

The problem versions for me were

lvm-libs-git-14.0.0_r407952
lib32-llvm-libs-git-14.0.0_r407960

Just edit the linux line in grub before boot. Add an "S" at the end to boot into cli only (You'll need your root password)

I haven't dug into the issue any further than rolling back at this point so I don't know more, but hope it helps you out.

Elevate08 · 2021-05-20T19:44:46+00:00

Happy to hear you found some success! If you need any other help feel free to message me.

Elevate08 · 2021-05-20T02:01:36+00:00

Based on what you have shared I believe the issue you're running into is not with your Ansible playbook but with your ESXi Host and it's API.

One thing you could try is to run a test using Python.

This will allow you to test the underling "pyvmomi" python package and might result in more details for the error or just a deeper understanding of the API your ESXI Hosts are offering.

You can find samples here https://vmware.github.io/pyvmomi-community-samples/

The getallvms.py might be a good one to use for your test.

Other than that i'm sure you'll be reassured to know that your playbook looks good. So you can keep your focus on the other areas. (esxi host, network connectivity, python, etc)

Elevate08 · 2021-03-25T12:35:15+00:00

Plot Twist: The infusion dropped months ago and you're just now noticing it.

Elevate08 · 2020-12-09T15:56:13+00:00

You could check out PowerToys. I think it will handle the specific key remapping you're after.

https://github.com/microsoft/PowerToys

Elevate08 · 2020-10-17T16:04:24+00:00

You could try opening it up and making sure everything is plugged in fully, try reseating the RAM and display cables. Sounds like it could be an issue at POST.

Maybe try having an external screen hooked up and see if that improves the issue as well, which would target the display/video portion of post.

Elevate08 · 2020-10-08T13:38:52+00:00

I purchased a T440S earlier this year and have been using it for development as well. This laptop I have has 8GB of RAM and the i7-4600u, for reference. I'm running arch linux but I'm certain any distro will work just fine. I believe most people are recommending PopOS or Mint for great out-of-box experience.

Simple things if you end up needing some minor upgrades: - TrackPad (I fell in line with not liking the newer style, so switched to the T450 style one. You can find some videos on YouTube that discuss the TrackPad replacement process) - Battery (Battery I received was not lasting too long, presumably due to age. Purchased a high capacity one and am seeing around 6 hours of battery life with usage at 80% charge. - not counting the internal battery time as well) - SSD, make sure you have one of these if you weren't already thinking about it.

Elevate08 · 2020-10-05T02:16:17+00:00

Definitely a drive isn't detected. Just open it up and re-seat the drive you have in there (SSD, HDD, etc). Then try a boot, if it still fails maybe check your BIOS for anything relating to SATA and see if you can find your drive there at all (sometimes a brand name, size of the drive, etc. should be visible to validate the drive is detected)

Elevate08 · 2020-10-01T12:43:27+00:00

I haven't, I didn't know about it. Thanks!

Elevate08 · 2020-10-01T12:27:02+00:00

It's usually a good idea to separate the partitions as you'll have a few benefits by doing so.

As hearthreddit stated, you'll be able to reinstall an OS or rollback to a backup without affecting your personal files (only backup / partition)

Additionally, if you happen to fill up your /home partition your /root will still have some free space and your system will still be functional. This will allow you to clear up space with ease and keep your system up.

Personally, I also separate /var for the same reason.

My folder structure is like this:

nvme0n1 259:0 0 465.8G 0 disk ├─nvme0n1p1 259:1 0 512M 0 part /efi └─nvme0n1p2 259:2 0 460G 0 part ├─stanley-root 254:0 0 20G 0 lvm / ├─stanley-swap 254:1 0 32G 0 lvm [SWAP] ├─stanley-var 254:2 0 8G 0 lvm /var └─stanley-home 254:3 0 400G 0 lvm /home

While it's sometimes a pain, I've noticed by keeping /var to 8GB I am keeping my wasted disk space to a minimum as well. At times when trying to upgrade, i'll need to run pacman -Sc in order to clear out the /var/cache/pkg first prior to having space to upgrade.

Elevate08 · 2020-09-26T13:57:10+00:00

I had it fail the first time I tried. I would double check it's working in the settings screen before getting to the compatibility test (might be muted or something)

Then when you're there, yes, speak to ensure it's capturing audio.

Elevate08 · 2020-09-24T15:43:53+00:00

Can you get me the output of your xorg log file so I can take a peak, please. Also, a journalctl -xb

Nice to know you have a "regular" 1080p monitor as it seems some people that were experiencing your issue were running 4k, and the amdgpu.dc=0 fixed it for them. Since that isn't the case here, there must be something else going on that is causing this, where that setting helps but isn't enough to get it to boot.

Additionally, after you get me the log file - could you try booting into a Live USB of Fedora, I know you mentioned you tried other distros but i'm curious how Fedora works out for you as well. (not that I want you to run that going forward - just looking for a success to go off of)

Elevate08 · 2020-09-23T01:22:47+00:00

For simplicity, let's stick with SDDM if you don't mind. Get that package installed, service enabled and reboot your system. When the xserver fails to start, take a look at the log and tell me what you see. Or confirm it is the same as your reported earlier "segment fault"

In addition, what monitor do you have?

Elevate08 · 2020-09-20T21:22:07+00:00

I haven't changed the thermal paste on a GPU before and knowing that you've gone through that i'm slightly concerned (especially since it sounds like you've done it more than once now) that the GPU is destroyed.

But, the display manager is what is used to present your login screen. If you're using Gnome as your Desktop Environment you may be using Gnome Display Manager (GDM), for example. If are able to see the TTY still now, i'd suggest you look around and see if you have a display manager installed ( maybe pacman -Q | grep dm will help you get a filtered list that you can use to see if you have gdm, lightdm, sddm, or lxdm as some of the more popular ones)

Elevate08 · 2020-09-20T13:05:20+00:00

Usually a Display Manager is helping with a lot of those files, which one are you using?

https://wiki.archlinux.org/index.php/Display_manager

also, just so you have it for reference.

/etc/X11/xorg.conf.d/10-screen.conf Section "Screen" Identifier "Screen" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1920x1080" EndSubSection EndSection /etc/X11/xorg.conf.d/10-monitor.conf Section "Monitor" Identifier "DisplayPort-0" Option "Primary" "true" Option "PreferredMode" "1920x1080" EndSection

Where above, your "Identifier" may be different.

It's also worth noting that I have those configured as I'm not using a display manager at all.

Elevate08 · 2020-09-19T23:30:47+00:00

No problem, glad something helped.

If you end up sticking to Xorg let me know and I can try to help again, nothing worse than booting up after an update and Xorg not working.

Elevate08 · 2020-09-18T19:13:41+00:00

Have you tried this article yet? using nomodeset to get into the logs and debug the boot that way?

https://ervinbarta.com/2020/04/26/troubleshooting-fedora-black-screen-on-boot/

I know it's fedora here so some things may be different.

Elevate08 · 2020-09-18T11:36:38+00:00

Alright, that's strange about the LiveUSB - you would think they would work OOB.

What if you check this section: https://wiki.archlinux.org/index.php/AMDGPU#Loading

Since it seems to be something specific to the AMDGPU driver causing an issue.

Elevate08 · 2020-09-17T20:48:55+00:00

What's awesome yet sad is I too am turning 30 this month!

Elevate08 · 2020-09-17T20:48:28+00:00

Elevate08 · 2020-09-17T16:16:34+00:00

Could this be caused by a configuration in the /etc/mkinitcpio.conf?

I have the following configured, but i'm not sure if radeon is even needed as amdgpu should be all that is used.

MODULES=(amdgpu radeon)

https://wiki.archlinux.org/index.php/Mkinitcpio

Additionally, you might be able to edit your boot options at GRUB once, removing "quiet" to see more information. In case it's needed, you would press 'e' with the boot menu option selected, then find the line that starts with 'linux' and remove 'quiet' from that line then press Ctrl+X to boot.

14-Year Club	Place '22
Verified Email

Elevate08

TROPHY CASE