Glassed Silver

I'm not using the multi-user ability of the application and just use the default user for myself with a custom password, so I cannot comment on how or if it can be done like that, but the application's author is surely going to be a better source of information. I can only provide support for the template itself and of course will help with anything I've gathered experience with so far on my own. But maybe someone else can voice in? Anyhow, wish you all the best with the application, it is quite mighty and useful indeed. Cheers!

Now I don't run cache drives YET, but this is scary! I hope this gets fixed soon!

It is working on my end... Maybe try deleting and re-adding the template with a clean config and cleared folders?

Currently there is an issue keeping you from running this container. If you haven't updated yet, wait a little. If you are looking to initially set this up, it won't function atm. Stay updated. https://github.com/happypandax/happypandax/issues/210

Archivebox has a new release (0.4.x) and it needs some new configuring. Would be hella awesome if you could look into it!

How about easy zero-conf (mDNS) networking? What I mean is: unRAID already announces itself in the network using mDNS as "Tower" (http://tower.local) How about adding just barely enough reverse proxy functionality to unRAID so I can from the docker and maybe even VM tab assign subdomains to my services? Not as a replacement for IP:Port, but to compliment it... e.g.: plex.tower.local ubuntu-vm.tower.local nextcloud.tower.local etc... Yes, that would be local access only, https with self-signed certs, why not, not really necessary to me, but I don't want to say no. The reason of my frustration? Well... If you really want to know, any other path is really, really annoying: Click Cheers!

TIL there is a ZFS plugin for unRAID. Although I'm extremely wary of a scenario in which my filesystem is supported through a plugin... eh

This may be related: https://github.com/rr-/szurubooru/pull/310 Alternatively it might be that this project is using a middleware to interface with youtube-dl that might be borked a little. That’s the case for youtubedl-material as well and one of the reasons why I have yet to release my CA for that application. Keep in mind, might be a good idea to share your experience at the official bug tracker either for assistance or to help find a bug others simply haven’t run into or noticed yet. As for the other two questions I think someone else will have to fill in. Cheers!

Very interesting. It should not be underestimated that not only a server can centrally host files and services, it can also have it's own locked-down policies that you wouldn't necessarily like to set on your desktop, because it might hinder your workflows too much. Talk about truly combining the strengths of both. Add backups to the mix and you're looking at incredible data protection. Now if we could have true bit rot protection in unRAID baked-in, that'd be incredible...

If anyone else has trouble accessing their fresh Yacy installation, here's what I found in the official documentation: Probably useful to put that in the description of the CA as well, @A75G. Cheers!

I configured it only through the settings interface in HPX itself, however first thought that comes to my mind is that you may wanna check the permissions of your yaml.

HappyPandaX is specifically made for doujinshi. (edit: added link to Wikipedia article for doujinshi, maybe it's a good idea to bring that term closer to an audience that hasn't come into contact with it so far? It is a pretty niche medium in the Western world after all. No hard feelings) It's also still in development. I am by the way not the developer, so I don't even claim to be the PR rep, not quite sure why we're arguing about functionality that HPX doesn't supply (yet) when it does provide functionality that Ubooquity doesn't have. It's a bit of an apples and oranges comparison. You can read up about what HPX is for on their Github page, which I linked in the CA info for the template. Either you find a use for it or you don't. I don't even claim that it's a good utility for manga in general or even more broadly comics in general. I use something else for manga and comics myself, which I told you right away. It is however excellent (from my observation, SO FAR! still testing myself mind you) for doujinshi. If you don't even deal with Doujinshi I'm sure you are - at least for now - way better off with software like Ubooquity that specializes in supporting more mainstream forms of readable illustrations like comics and manga. It is not (so far at least, although I don't thinkk there are great ambitions to that...) a Ubooquity competitor.

Hey, thank you for the interest in the subject in general. I can only tell you where I am coming from and why I picked it, I'm sure many folks may handle their needs differently. Everyone has different priorities and desires after all. So here is why I picked HPX for my doujinshi needs: It has metadata scrapers built-in (through plugins) for the two staple sites to download doujinshi from (nhentai and ExHentai) as well as a plugin for reading metadata stored in an accompanying text file. This makes organizing a doujinshi collection, browsing it and discovering forgotten gems within your own collection a much smoother experience. I am well aware there are plugins for calibre as well (I don't know about ubooquity), but calibre REALLY isn't made for this kind of medium as you'll be generating a lot of custom fields and I'd rather keep calibre, which I do use for fanfics and traditional books a good solution for what I throw at it rather than half-ass maintaining calibre. HPX will also provide you with a beautiful WebUI to manage everything from, it has an API which the official HPX desktop client interfaces with as well, but I haven't gotten latter one to run yet. However all data in HPX is portable and I really like that. There is quite a few things very specific to doujinshi that make maintaining them in a traditional system not specifically made for it possible but less than ideal. So when I saw that there was a pretty popular tool for running a doujinshi server on github I jumped into it and created a little demo library. So far I'm liking it a lot and that's why I threw together a CA template for it so more people can try it and maybe get to like it as well. The project may not have been updated in half a year now, but the dev is still active in the issue tracker and I believe that the state of the application right now already far exceeds anything else I've so far looked into to consider serving my doujinshi. As for regular manga that are published properly and aren't doujinshi I'm using komga, but I am not quite satisfied with that so far. Just a few stones on the path to having a good download-managa-server-sync-reader stack there though. Rambling aside though, I don't need my doujinshi THAT portable, so if they only chill on my server and no Android reader app ever comes up to sync it to then I'll be fine. That'd be a limitation of HPX so far, at least until someone creates an Android app for the API which is after all possible. Hope that clears it up a bit for you. If you have any further questions, go ahead and ask. PS: Yes, interfacing metadata scraping with doujinshi.org would be nice, iirc that's planned as well.

Please note: The author of the application is aware that the software needs rework. This is ongoing at the moment, so if you find the application to be a bit hard to work with, maybe you want to be a bit patient and wait for the rework progressing. As it is now, with fiddling the app can be made to work, but it's not very smooth. I still think this application provides a great benefit to the community of doujinshi collectors and am not going to pull the (marked as beta in CAs as before) template for it. Thank you and happy reading! _______________________________________ Hello and I am glad you're stopping by to check out this support thread for my CA template for HappyPandaX. From the application's author: This application itself is released in alpha-stage by the author themselves and this CA template is in beta. I would appreciate if you could help me test this application. There are some known issues, e.g. downloading from Exhentai is limited to being logged in (go into About > Plugins and install the plugins that are available for a stock installation, click on "Open Plugin Site" for the EHentai Login plugin. Follow the instructions and help from there) and having credits for downloading available. As for downloading from other pages, so far no luck for me on nhentai, however scraping metadata for existing doujinshi is working fine for me. You can stage your scans and metadata scrapes before you commit them to your collection. (Add > Scan) GitHub Link Application Author's Patreon, if you wanna support them Documentation The creator also is an artist and links to their various outlets on Patreon and Twitter. Support for this CA in the context of the CA implementation is provided by me, however do keep in mind the application is alpha, the CA beta. Change Log (just the unRAID CA template) 2020 June 1: Initial release to CAs Cheers and happy organizing!

I haven't released the container in the CAs yet for a reason... Beta tag or not, there's just a few too many rough edges that I noticed myself already for me to feel that it's CA-beta time. It launches standard youtube-dl behavior. If 8k is available it will download that. The simulated youtube-dl command can be previewed before issuing the download command, then you can dissect the particular args each on youtube-dl's documentation which is lengthy and unwieldy. That is also one of the goals of the project, to make args a) more structured and b) explain them better by wrapping them up - gradually - in a GUI settings panel. A central place to issue youtube-dl commands through any possible means. API, web interface, extensions (Firefox and Chrome-based).

I see you're providing a youtubedl-material container. The only reason I haven't published my own container for this to the CAs yet is because I'm waiting for some bugs and blemishes to be ironed out. The project maintainer and I are working together on this. Either way good to see this application getting some well deserved attention.

My browser is never under 30 tabs on my desktop alone. I feel you. [emoji14] Gesendet von meinem SM-N960F mit Tapatalk

Hmm, my issue is about huginn, but I got what you're saying I'll inquire at https://github.com/huginn/huginn For anyone interested, I created an issue over at the official huginn github page. If any Googlers or anyone with an idea wants to check it out: click Cheers!

Yep. The first 4 lines are actually the remainders of the shutting down state. (I restarted the container to get a log for the start up sequence and snipped a little to early into the log, sorry for the confusion) Nothing gets logged after the stdout entered RUNNING state message. (except for when I shut down the container obviously.) But nothing in the logs when I try to access the WebGUI.

Nope, all defaults!

I didn't assume you were the developer, but I am particularly fond that you created this CA anyhow. Having said that, still would love to know if the different formats that ArchiveBox is supposed to generate are generated ok on your end? All the format flags in the template are set to true, so that can't be it. But PDF, screenshot and output.html aren't being generated. (well actually output.html is generated, it's just a 0kb file, the rest isn't even an empty file on disk) I'll merrily look into this when I have more time on the github of the project, however since we have the same setup kinda I thought I might ask here first.

Thanks a bunch! I fixed my wallabag and now am looking into getting my Firefox history (from a Windows desktop, mind you) to automatically get scraped. The instructions on the project's github page seem to assume you run ArchiveBox on a Linux desktop on which the installation of Firefox is running. That clearly isn't the case though here. Would love to do several automatic scrapes with cron jobs. a) a defined watched.txt with manual entries. Already set that up, easy! b) an automatically syncing history and bookmarks file of Firefox and maybe even Chrome. (I only use Chrome occasionally, but hey, whilst I'm at it...) c) constantly watching a Pocket/Wallabag list. d) maybe more? Curious to maybe throw huginn into the mix to even backup sites that are possibly interesting and that may be pulled. Fan games for example. (notorious example: Nintendo-based fan games...) Really stoked to jump into a whole new dimension of independence! I take you not replying to the transition to v0.4 as a positive sign? As in, it won't affect us? Either way, better to start archiving now than later. Even if there is structural breaking change I guess. Again, thanks so much for offering this container. I requested it on the CA wishlist github repo and here we are, a few weeks later with a working solution!

Hey! First of all thank you for the huginn container, I've read a bit about it and it seems to be a feasible self-hosted alternative to IFTTT which I love and use happily almost since the beginning. Never bad to fight back a little more control though, so here I go... Unfortunately I cannot get the WebGUI to show up? Here's the log: 2020-04-20 10:06:46,378 WARN received SIGTERM indicating exit request 2020-04-20 10:06:46,378 INFO waiting for stdout to die 2020-04-20 10:06:49,382 INFO waiting for stdout to die 2020-04-20 10:06:49,383 INFO stopped: stdout (terminated by SIGTERM) The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x86-mswin32, x64-mingw32. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32`. Using rake 12.3.3 Using ace-rails-ap 2.0.1 Using concurrent-ruby 1.1.5 Using i18n 1.6.0 Using minitest 5.11.3 Using thread_safe 0.3.6 Using tzinfo 1.2.5 Using activesupport 5.2.2.1 Using builder 3.2.3 Using erubi 1.8.0 Using mini_portile2 2.4.0 Using nokogiri 1.10.8 Using rails-dom-testing 2.0.3 Using crass 1.0.5 Using loofah 2.4.0 Using rails-html-sanitizer 1.0.4 Using actionview 5.2.2.1 Using rack 2.0.8 Using rack-test 1.1.0 Using actionpack 5.2.2.1 Using nio4r 2.3.1 Using websocket-extensions 0.1.3 Using websocket-driver 0.7.0 Using actioncable 5.2.2.1 Using globalid 0.4.2 Using activejob 5.2.2.1 Using mini_mime 1.0.1 Using mail 2.7.1 Using actionmailer 5.2.2.1 Using activemodel 5.2.2.1 Using arel 9.0.0 Using activerecord 5.2.2.1 Using mimemagic 0.3.3 Using marcel 0.3.3 Using activestorage 5.2.2.1 Using public_suffix 3.0.2 Using addressable 2.5.2 Using jmespath 1.1.3 Using aws-sdk-core 2.2.15 Using bcrypt 3.1.12 Using msgpack 1.2.4 Using bootsnap 1.3.0 Using kaminari-core 1.1.1 Using kaminari-actionview 1.1.1 Using kaminari-activerecord 1.1.1 Using kaminari 1.1.1 Using bundler 1.17.3 Using method_source 0.9.2 Using thor 0.19.4 Using railties 5.2.2.1 Using sprockets 3.7.2 Using sprockets-rails 3.2.1 Using rails 5.2.2.1 Using bootstrap-kaminari-views 0.0.5 Using buftok 0.2.0 Using coffee-script-source 1.12.2 Using execjs 2.7.0 Using coffee-script 2.4.1 Using coffee-rails 4.2.2 Using cookiejar 0.3.2 Using daemons 1.1.9 Using declarative 0.0.9 Using declarative-option 0.1.0 Using delayed_job 4.1.5 Using delayed_job_active_record 4.1.3 from https://github.com/dsander/delayed_job_active_record.git (at rails52@8efc7b1) Using orm_adapter 0.5.0 Using responders 2.4.1 Using warden 1.2.8 Using devise 4.6.2 Using unf_ext 0.0.7.4 Using unf 0.1.4 Using domain_name 0.5.20170404 Using dotenv 2.0.1 from source at `vendor/gems/dotenv-2.0.1` Using dotenv-rails 2.0.1 from source at `vendor/gems/dotenv-2.0.1` Using hashie 3.5.6 Using multi_json 1.13.1 Using multipart-post 2.0.0 Using faraday 0.12.1 Using jwt 1.5.6 Using multi_xml 0.6.0 Using oauth2 1.4.0 Using dropbox-api 0.5.0 from https://github.com/dsander/dropbox-api.git (at 86cb7b5@86cb7b5) Using eventmachine 1.2.7 Using em-socksify 0.3.0 Using http_parser.rb 0.6.0 Using em-http-request 1.1.2 Using equalizer 0.0.11 Using polyglot 0.3.5 Using treetop 1.6.9 Using erector 0.10.0 from https://github.com/dsander/erector.git (at fix-fixnum-warning@9ee3667) Using et-orbi 1.0.9 Using ffi 1.9.25 Using ethon 0.12.0 Using evernote-thrift 1.25.1 Using oauth 0.4.7 Using evernote_oauth 0.2.3 Using faraday_middleware 0.12.2 Using sax-machine 1.3.2 Using feedjira 3.1.0 Using sass 3.4.23 Using font-awesome-sass 4.7.0 Using forecast_io 2.0.1 Using foreman 0.63.0 Using geokit 1.8.5 Using geokit-rails 2.2.0 Using little-plugger 1.1.4 Using logging 2.2.2 Using memoist 0.16.0 Using os 0.9.6 Using signet 0.7.3 Using googleauth 0.5.1 Using httpclient 2.8.3 Using mime-types-data 3.2016.0521 Using mime-types 3.1 Using uber 0.1.0 Using representable 3.0.4 Using retriable 3.0.2 Using google-api-client 0.13.0 Using google-cloud-env 1.0.0 Using google-cloud-core 1.0.0 Using google-cloud-translate 1.0.0 Using haversine 0.3.0 Using httparty 0.14.0 Using hipchat 1.2.0 Using httmultiparty 0.3.16 Using http-cookie 1.0.3 Using http-form_data 1.0.1 Using http 2.1.0 Using huginn_agent 0.4.0 Using hypdf 1.0.10 Using jquery-rails 4.2.2 Using json 2.3.0 Using to_regexp 0.2.1 Using jsonpath 1.0.1 Using kgio 2.10.0 Using kramdown 1.3.3 Using libv8 7.3.492.27.1 (x86_64-linux) Using liquid 4.0.3 Using rb-fsevent 0.10.2 Using rb-inotify 0.9.10 Using listen 3.0.8 Using systemu 2.6.4 Using macaddr 1.7.1 Using memoizable 0.4.2 Using mini_magick 4.9.5 Using mini_racer 0.2.9 Using mqtt 0.3.1 Using mysql2 0.5.2 Using naught 1.1.0 Using net-ftp-list 3.2.8 Using netrc 0.11.0 Using omniauth 1.6.1 Using omniauth-oauth2 1.3.1 Using omniauth-37signals 1.0.5 Using omniauth-dropbox-oauth2 0.3.0 from https://github.com/bamorim/omniauth-dropbox-oauth2.git (at 3504670@3504670) Using omniauth-oauth 1.1.0 Using omniauth-evernote 1.2.1 Using omniauth-tumblr 1.2 Using omniauth-twitter 1.3.0 Using omniauth-wunderlist 0.0.2 Using raindrops 0.17.0 Using rb-kqueue 0.2.4 Using rest-client 2.0.2 Using rturk 2.12.1 Using uuid 2.3.7 Using ruby-growl 4.1 Using rufus-scheduler 3.4.2 Using tilt 2.0.7 Using sass-rails 5.0.6 Using select2-rails 3.5.9.3 Using simple_oauth 0.3.1 Using slack-notifier 1.0.0 Using spectrum-rails 1.3.4 Using tumblr_client 0.8.5 from https://github.com/albertsun/tumblr_client.git (at e046fe6@e046fe6) Using twilio-ruby 3.11.6 Using twitter 5.15.0 from https://github.com/sferik/twitter.git (at master@d11707e) Using twitter-stream 0.1.15 from https://github.com/cantino/twitter-stream.git (at huginn@a80822d) Using typhoeus 1.3.1 Using uglifier 2.7.2 Using unicorn 5.1.0 Using weibo_2 0.1.7 from https://github.com/albertsun/weibo_2.git (at master@ac38d04) Using xmpp4r 0.5.6 Bundle complete! 109 Gemfile dependencies, 182 gems now installed. Gems in the groups test and development were not installed. Bundled gems are installed into `./vendor/bundle` 2020-04-20 10:07:12,962 INFO Included extra file "/etc/supervisor/conf.d/bootstrap.conf" during parsing 2020-04-20 10:07:12,962 INFO Included extra file "/etc/supervisor/conf.d/foreman.conf" during parsing 2020-04-20 10:07:12,962 INFO Included extra file "/etc/supervisor/conf.d/mysqld.conf" during parsing 2020-04-20 10:07:12,976 INFO RPC interface 'supervisor' initialized 2020-04-20 10:07:12,976 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2020-04-20 10:07:12,976 INFO supervisord started with pid 1 2020-04-20 10:07:13,979 INFO spawned: 'stdout' with pid 560 2020-04-20 10:07:13,980 INFO spawned: 'bootstrap' with pid 561 2020-04-20 10:07:13,989 INFO success: bootstrap entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-04-20 10:07:13,996 INFO exited: bootstrap (exit status 1; not expected) 2020-04-20 10:07:15,000 INFO success: stdout entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Grateful for any pointers!

Aaaaaah! But that's something I might as well just put into the container's shell command prompt, right? No need to edit in and out post args, right? My personal investigation is that with cleared args the container just stops... Isn't the whole point of such a container to also do pulls on demand? Ideally with a page where I just drop a URL? Also, do you have any idea how smooth the transition to the v0.4 branch will be? I know the dev has been delaying the release of it outside of beta stage for a long while now, but the release is going to come around eventually, if the transition is rough, maybe it's better to start this docker on the unstable 0.4 in CA beta status and then just hang on tight until 0.4 final drops and reflect that change in removing the beta flag in the CA as well? Sorry if the questions seem a bit silly, never really looked in the codebase for this project, I just know that I love the approach this application has over similar ones since it saves in many formats and even (will?) support dynamic content. Oh and I have a second question! I am also trying to use your wallabag container, however the layout it completely borked. Maybe you can give me any pointers? Cheers and thanks a lot for your work!

I edited the post command to be "./archive (URL,FEED,BOOKMARK,FILE)" (no quotes) and now the updating of the container fails...? Also a bit sad that the web server isn't built-in, I don't really intend to run a reverse-proxy, mostly because all the guides out there focus on exposing services to the internet and setting up a domain, etc... which I am not interested in one bit. At least not right now. All I want is service-name.<server-name>.local if anything. Maybe I'm just not too pressured to look into those tutorials and stripe out the extra complexities like domains etc that I don't need, then again I don't know how much those guides rely on you following the exact procedure. Is ANYONE reverse-proxying their services for their LAN only with the intention of .local and no publicly certified secure certificates? Hmm... (unless Let's Encrypt also works with local-only domains?)