geeseven

Results 27 comments of geeseven

I am able to get [Qubes OS][0] and [DBAN][1] ISOs to work on a system that only has legacy BIOS. Both [Lakka][2] and [LibreELEC][3] generic IMGs gave me an error...

The following Alpine Linux ISOs work: alpine-extended-3.12.0-x86_64.iso alpine-standard-3.12.0-x86_64.iso The following ISOs do not work: alpine-extended-3.12.0-x86.iso alpine-standard-3.12.0-x86.iso Here is the error: ![error](https://i.imgur.com/POLLrGm.png) ventoy 1.0.19 legacy BIOS

Hey @David-Development, I was theory-crafting and came up with the following cons for replacing the 'mark all as read' with 'mark all as read and refresh': - Users wanting to...

Hey @emasty, Thanks for the timely reply. > "Currently when I have numerous new articles, I go folder by folder and marking each folder as read as I go through...

> use curl in a local (bash) script to iterate over all to be imported URLs and push them to the `/import` route. The only thing to be considered there...

> Apart from the fact that I was not able to fetch any recipe from the URL in the command I should have not included a foodnetwork.com recipe in my...

> "This request is not allowed to access the filesystem" I released that I was using an 'app password' where I had removed 'Allow filesystem access'. Once I enabled that,...

@christianlupus ```console $ ./import-cookbook.sh temp https://www.chefkoch.de/rezepte/1807401292413281/Zwiebelsuppe-nach-Art-der-legendaeren-Pariser-Marktfrauen.html added https://www.chefkoch.de/rezepte/1807401292413281/Zwiebelsuppe-nach-Art-der-legendaeren-Pariser-Marktfrauen.html "Another recipe with that name already exists" https://example.com "Could not find recipe element" $ cat temp https://www.chefkoch.de/rezepte/1807401292413281/Zwiebelsuppe-nach-Art-der-legendaeren-Pariser-Marktfrauen.html https://www.chefkoch.de/rezepte/1807401292413281/Zwiebelsuppe-nach-Art-der-legendaeren-Pariser-Marktfrauen.html https://example.com $ cat import-cookbook.sh...

@mrzapp, I agree that this script should only be used as a stop gap till a proper solution is developed. Where should the documentation folder be located?

I am starting to have mixed thoughts on a `/documentation` folder, if it is only going to contain a stop gap script. Kinda seems misleading to me. What about something...