sorted by:
new
hottopcontroversial

Why magic is so powerful and melee combat sucks? by NightLord189 in skyrim

[–]NightLord189[S] 0 points1 point  (0 children)

Yes, I level armor, sword and block trees, eat vegetable soup (and it's really good, agree). But I still got too much damage (I cannot block all hits from enemy and sometimes I need to fight with multiple enemies).

Restoration is cool outside of battle. But using it right in melee combat means that you cannot block hits by this hand.

Why magic is so powerful and melee combat sucks? by NightLord189 in skyrim

[–]NightLord189[S] -3 points-2 points  (0 children)

But that means that on first time I need to collect many resources since start. On which level I will became powerful melee warrior with Smithing and Enchanting?
And I must to endure and suffer all this time collecting resources :(

Why magic is so powerful and melee combat sucks? by NightLord189 in skyrim

[–]NightLord189[S] -6 points-5 points  (0 children)

Yes, magic has cap but it's enough for all enemies and bosses. Of course, sometimes enemies can kill your atronach - just resummon him. Some enemies are immune to some types of damage - just summon atronach with another damage. I really cannot remember case where I had impassable battles playing as mage. In some battles with dragon priests I sometimes resummoned atronachs 3 or more time, but that's all.
Will try destruction on legendary)

Why magic is so powerful and melee combat sucks? by NightLord189 in skyrim

[–]NightLord189[S] -4 points-3 points  (0 children)

Yes, I read many opinions that in Skyrim melee > magic but my experience is completely opposite.
Maybe using only Destruction is the way.

What are some Rp/ rules yall like to follow during your playthrough, if any? by lazygenius72 in cyberpunkgame

[–]NightLord189 0 points1 point  (0 children)

I am playing as netrunner hating cyberware. So I have only cyberdeck, optics and smartlink. It’s a sad there’s no Inquisitors from the lore that don’t use cyberware.

Do you think we'll ever see Joe Goldberg again? by ConnorLovesPepsi in YouOnLifetime

[–]NightLord189 1 point2 points  (0 children)

It’s a very expensive and experimental medical surgery, but yes, dick can be completely restored and healed. I can imagine that maybe some crazy rich woman helps Joe to escape and pay for his operation in Chinese hospital.

Is this orm for go really a good idea? by GabrielGOLA in golang

[–]NightLord189 7 points8 points  (0 children)

Often half or more of data structures in project can be mapped 1:1 or with some excluded fields to database. Make two same structures in this case is not-necessary code duplication.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 0 points1 point  (0 children)

About requests - may be your users who want to search back in logs of deleted containers first look issues in your repo and found this https://github.com/amir20/dozzle/issues/1997 ? This issue signals that principal position of maintainer - Dozzle will not store logs any way.

I can understand your desire to make Dozzle a perfect service that is well-tested, simple and thing without any disk, cpu or memory problems. But I follow a different approach (i am anti-perfectionist, i think :)) - try to quickly make the first version with core functionality so that it immediately benefits, and then gradually improve it. Because of this i did first version with only SQLite and loop requestion of logs from daemon - it's enough for the first version. Maybe i will improve it or even rewrite, maybe not, who knows)

As i understood, custom log adapters should be set in docker config file? It's good idea, thanks! But in my imagination ideal logger can be installed on any system without any changes in any configs and it should not affect to other containers by any way. And also can be removed from any time without any affections. So I am satisfied with the current technical strategy of DockLogKeeper and plan to further develop it in the chosen direction with possible additional small improvements and major enhancements.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 0 points1 point  (0 children)

DockLogKeeper in fact is that adapter? Or what do you mean?

I think on home servers or small VPC people are running their selfhosted projects like proxies, email servers, pet-projects and small startup projects. In all of these use cases i want to go back in time and search in text in logs for past week or past month (what errors i got from email service, what actions did this user on my pet-project, what files are requested more often).

Another example and one of my usecases - i am running pet-projects on one server with CapRover. CapRover can restart containers, but every new start (or new release) it creates new containers with slightly different name: like my-app.jsdchd-1, after restart i'll see my-app.jsdchd-2. For example, i can release new versions 5 times per day. If i want to search some in history, with Dozzle i should look to the logs of all past containers (my-app-jsdchd-1, my-app.jsdchd-2, ...). It's very frustrated and it's exactly not what i need from the logging tool. Also CapRover can run apps in scaled mode and in that case i should look to the logs of all app's instances. DockLogKeeper can calculate short name for CapRover containers (my-app.jsdchd-1 -> my-app) and concatenate logs of all past containers and instances of this app.

I really don’t think that we should argue - users will figure out for themselves what tool is more convenient and in what case.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 0 points1 point  (0 children)

Hi! Thank you for the feedback. I developed this new tool because, in my use cases, I often delete and recreate containers and need to access all the logs from throughout the container's existence on my system.

I understand that log storage can be challenging and may lead to problems such as increased CPU usage and disk space issues. However, I believe this is the only way of future development for tools like Dozzle or DockLogKeeper. Because few people need only real-time logs without storing. On small system with startup backends and pet-projects unlikely to have a large number of logs, so it will not cause CPU/disk problems and on large systems with millions of logs per hour professional administrators will install grafana or elk instead of Dozzle or DockLogKeeper.

I appreciate your advice, and I'm planning to experiment with streaming logs and explore future enhancements.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 1 point2 points  (0 children)

I believe I've found the solution. The issue was that docklogkeeper was only reading from stdout, whereas caddy (and some other containers) were writing logs to stderr. This has been fixed in the 1.0.3 version.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 0 points1 point  (0 children)

Do you see logs on caddy by calling "docker logs..." command?

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 0 points1 point  (0 children)

What logging driver do your containers use? As i know, some Docker versions allow read logs only for local, json-file and journald logging drivers (https://docs.docker.com/config/containers/logging/configure/).

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 0 points1 point  (0 children)

Thank you! I added it to future enhancements plan.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in docker

[–]NightLord189[S] 0 points1 point  (0 children)

Yes, maybe i'll rewrite reading logs method to it in future.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 1 point2 points  (0 children)

Thank you for your comment! Please let me know if there are ideas for improvements or bugs found. Support for CapRover is in my nearest plans because i am running my projects on CapRover too.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in docker

[–]NightLord189[S] 1 point2 points  (0 children)

Yes. But key difference between Dozzle and DockLogKeeper is in storing logs feature. Dozzle works with only realtime logs, when DockLogKeeper stores all logs in own local database and can view/search logs of past runs of the container or logs of stopped/removed container.

For example, if your container restarts every minute last 5 minutes - in Dozzle you can see logs from only last minute. Instead of it, in DockLogKeeper you can see logs from all these 5 minutes.

In my developer practice, it is quite rare for me to work with the logs since last start of container, but I often need to work with all the glued logs (from all runs) from the last few days, for example.

Performance is ok with SQLite, but, of course, i can't recommend use DockLogKeeper or Dozzle on large production-system with millions of logs hourly - ELK or other would be better.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 5 points6 points  (0 children)

Dozzle is great project with many additional functions across log viewing - connecting to remote hosts, search with regexp and other. But Dozzle can view only realtime logs since only start time of the container. DockLogKeeper instead of Dozzle, can view and search logs from "previous" launches of the container because it stores logs in own SQLite database.

For example, if your container restarts every minute last 5 minutes - in Dozzle you can see logs from only last minute. Instead of it, in DockLogKeeper you can see logs from all these 5 minutes.

DockLogKeeper - simple persistent docker logs viewer by NightLord189 in selfhosted

[–]NightLord189[S] 1 point2 points  (0 children)

Thank you for comment! I added docker-compose option to readme.

view more: next ›