54
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

Might be related to this other post: https://lemmy.ca/post/24478184

crosspost content below:


Firstly, this post is not to celebrate somebody losing their job, nor to poke fun at a company struggling in today's market.

However, it might go some way to explaining why Portainer are tightening up the free Business plan from 5 to 3 nodes

https://x.com/theseanodell/status/1809328238097056035

Sean O'Dell

My time at Portainer came to an end in May due to restructuring/layoffs. I am proud of the work the team and I put in. Being the Head of Marketing is challenging but I am thankful for the personal growth and all that we accomplished. Monday starts the search for my next role!

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 15 points 1 week ago* (last edited 1 week ago)

I also saw a post about a portainer alternative, anyone know others?

Monitor (docs.monitor.mogh.tech) (from the other site)

  • "core API and periphery agent are written in Rust"
  • Nice UI & lots of features
  • I wish it had a different name because "Monitor" is very hard to search with

DockGe from the other post

  • Looks like it's popular, from the other post

  • Features are more limited, no environment variables yet I don't think

[-] [email protected] 12 points 1 week ago

I rolled out Dockge the other week, and it's solid. It can handle environment variables, but lacks other portainer features like controlling networks, volumes, building images, etc.

One big plus is that Dockge works really well with the dockcheck.sh script for updates, where as Portainer breaks that script.

[-] [email protected] 5 points 1 week ago
[-] [email protected] 2 points 1 week ago

I started with Yacht and moved to Portainer. Yacht's ui was just too heavy and unresponsive for me. I got logged out of sessions without it actually telling me almost every time I used Yacht. I would have to log out and in again just to use it (a process that often freezed up as well for reasons I cannot comprehend). I finally had enough and switched to Portainer; not a single complaint since.

[-] [email protected] 1 points 1 week ago

Yacht is pretty much unmaintained.

[-] [email protected] 1 points 1 week ago* (last edited 6 days ago)

Used it for a bit but I didn't like how you have to deploy things from templates which are basically compose files that don't look like compose files.

[-] [email protected] 1 points 1 week ago

They're 1-1 compose files.

The app just saves them as compose files and then runs docker compose in the backend.

it is EXTREMELY barebones

[-] [email protected] 2 points 1 week ago

I put the sample template (https://yacht.sh/docs/Templates/Templates/) into a file named docker-compose.yml and Docker said the syntax was invalid. Are you saying I can give Yacht a compose file and it's cool with it?

[-] [email protected] 1 points 1 week ago

Ah, no not the template files for the individual containers, but the project descriptors are just compose files.

[-] [email protected] 4 points 1 week ago

I've heard of dockge as a lightweight alternative to portainer.

[-] [email protected] 3 points 1 week ago

There are some things that are easier to see and check in Portainer, but for pure compose handling (up, down, logs) dockge works really well.

[-] [email protected] 4 points 1 week ago

The thing about dockge is that it’s easy to go to and from using it. It can scan existing folders for compose files, and because it uses compose files itself, you could just as easily start containers made by dockge without dockge even running.

Of course, this means it lacks some of the fancier features of something like portainer, but I personally enjoy the simplicity

[-] [email protected] 2 points 1 week ago
[-] [email protected] 1 points 1 week ago

Dokemon and monitor seem to be the best alternatives in this thread so far.

[-] [email protected] 1 points 1 week ago* (last edited 1 week ago)

Another risk with Monitor, which may get better with time. Is that FOSS rust projects have a tendency to slow down or even stall due to the time cost of writing features, and the very small dev community available to pick up slack when original creators/maintainers drop off, burn out, or get too busy with life.

To be clear: I have nothing against rust. It's a fantastic language filling in a crucial gap that's existed for decades. However, it's I'll suited for app development, that's just not it's strength.

this post was submitted on 06 Jul 2024
54 points (100.0% liked)

Selfhosted

37923 readers
463 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS