Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SQ
Posts
17
Comments
312
Joined
2 yr. ago

  • The battle of Britain was a very close thing and if the Germans had used a slightly different strategy, they could have won. Given that America was not yet in the war and there was an alliance with the Soviet Union, could you explain why the Germans could not have proceeded with operation sealion bearing in mind that the allies did essentially the reverse 4 years later?

  • So if Germany had proceeded with operation Sealion - invasion of Britain- and succeeded, but not with operation Barbarossa - invasion of soviet union, could they not have won? There would be nowhere in Europe for North Americans to muster and USA would likely remain neutral (pre Pearl Harbor). Germany would get British colony oil and only have to defend against Soviet attack.

  • GitLab just doesn't compare in my view:

    To begin with, you have three different major versions to work with:

    • Self-Hosted open source
    • SAAS open source
    • Enterprise SAAS

    Each of which have different features available and limitations, but all sharing the same documentation- A recipe for confusion if ever I saw one. Some of what's documented only applies to you the enterprise SAAS as used by GitLab themselves and not available to customers.

    Whilst theoretically, it should be possible to have a gitlab pipeline equivalent to GitHub actions, invariably these seem to metastasize In production to use includes making them tens or hundreds of thousands of lines long. Yes, I'm speaking from production experience across multiple organisations. Things that you would think were obvious and straightforward, especially coming from GitHub actions, seen difficult or impossible, example:

    I wanted to set up a GitHub action for a little Golang app: on push to any branch run tests and make a release build available, retaining artefacts for a week. On merging to main, make a release build available with artefacts retained indefinitely. Took me a couple of hours when I'd never done this before but all more or less as one would expect. I tried to do the equivalent in gitlab free SAAS and I gave up after a day and a half- testing and building was okay but it seems that you're expected to use a third party artefact store. Yes, you could make the case that this is outside of remit, although given that the major competitor or alternative supports this, that seems a strange position. In any case though, you would expect it to be clearly documented, it isn't or at least wasn't 6 months ago.

  • You can configure Jellyfin to automatically add new found items to your library but you will need to get on top your logs to make the most of this:

    • If you are getting scanning errors then you need to look into them
    • (Building on above) You will find that your OS has limits on how many file watchers it can have. You may need to update your config to accommodate changes.
  • I think you may have misunderstood your issue. 16 GB is more than is needed on / for a typical desktop Ubuntu installation. For example, here is a partial output of df -h on my Ubuntu 22.04 system- this is a server but it has a full desktop environment installed. I actually originally put 20.04 on it when that was current so it has accumulated some cruft. I also remove snaps:

    FilesystemSizeUsedAvailUse%Mounted on
    /dev/sda147G11G34G25%/
    /dev/sda784G26G54G33%/home
    /dev/sda688G22G62G27%/var

    The thing you're most likely running into is that whilst everyone quickly realises the advantages of putting /home on a separate partition, it's not so obvious that /var should be on a separate partition as well. This is because /var is where all the logs and caches are stored, and if you have a runaway process that fills up /var/log, it can cause the system to crash. Experienced Linux users will have encountered situations where /var was not on a separate partition and their box broke because of logs not being cycled...

    I realise that you may be saying that you have 16GB total for 2 x installations. That is going it a bit but should be possible with some thought and care. Good luck!

  • My reason for stipulating that is that lot of people saying it do so either from ignorance (they simply don't believe/understand that you might not be able to opt out) or on the basis of outdated information, e.g. "I bought my TV ten years ago and never had to do this". Your experience being in the recent past I guess I could try this as a sale stipulation point, thanks.