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 thread.
View all comments View context
5 points

There’s also Yacht.

permalink
report
parent
reply
1 point

Yacht is pretty much unmaintained.

permalink
report
parent
reply
2 points

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.

permalink
report
parent
reply
1 point
*

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.

permalink
report
parent
reply
1 point

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

permalink
report
parent
reply
2 points

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?

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 3.7K

    Monthly active users

  • 2K

    Posts

  • 23K

    Comments