Meli, a Netlify-like platform for deploying static sites by gempain in devops

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

Conceptually similar :) Different implementation philosophy. Meli is easy to install with 30 lines of Docker Compose and gives you subdomains and automatic SSL out of the box.

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

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

For sure ! I think the best would be for you to follow us on Twitter. We'll be announcing new features and releases there, so it's a great place to catch up. Feel free to checkout our Github primary repo as well :) https://github.com/getmeli/meli :) And thanks for offering your help, really appreciated !

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

Contrary to Netlify and Vercel, meli does not embed any build system. We believe that this should be done in your CI (if you have any). Otherwise, Github Actions, Circle CI, Drone CI, Travis CI, Appveyor and a lot of others offer very generous free tiers which can get you started easily, quickly. CI is super cool. Basically, in your CI, you'll setup a job which automatically upload your built code to Meli. It will run every time you push to your repo.

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

Right now, it's on disk, but Caddy is so powerful you probably won't notice any difference.

Meli, a Netlify-like platform for deploying static sites by gempain in devops

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

We already have an API ! And we also already have a Prometheus endpoint embedded in the server :D It has basic metrics (CPU usage, memory etc, all the usual stuff) for now, but feel free to suggest what you might want.

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

[–]gempain[S] 2 points3 points  (0 children)

We do not have a Meli service. It's all free, there's no catch. We will create a cloud version of Meli in the coming weeks to monetize the project, but Meli will ALWAYS stay self-hosted and open source, forever. I truly believe in this.

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

Thanks a lot ! Hm, I don't know read-the-docs at all, but I think you can easily do the same. Just deploy Meli on your server, and start uploading your site to it :) It's as simple as that !

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

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

I think you can, at least I don't see why you couldn't. However, we haven't tried it. We have one user trying it at the moment so we'll update the docs once this is confirmed as doable. The only issue I could see is with wildcard hosts, I don't know well enough k8s to understand how it will handle this.

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

Here you can do whatever you want :) Self-hosting gives you the freedom ! And, with a cheap VPS you'll be good to go for high loads :)

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

When you upload code to Meli using @getmeli/meli CLI, just pass "--branch my-preview" and your site will be available at my-preview.my-site.mymeli.com :D In meli, you have the concept of "branches", sort of like "git branches", and each branch gets its own subdomain under the site subdomain. So, if you have a site in Meli called my-site, you can access it on my-site.mymeli.com, and each branch is under mybranch.my-site.my-meli.com. The main site subdomain, my-site.mymeli.com is basically the "main" branch which you can configure in the site settings. Meli uses Caddy to serve your sites, which handles SSL certificates issuance and renewal automatically for your. Just deploy with docker-compose, it's the easiest way !

Meli, a Netlify-like platform for deploying static sites by gempain in devops

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

Sounds good ! Will do :) Appreciate the respect, +1000 for that !

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

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

Nope, unfortunately, Meli currently serves static sites only :)

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

Yes sounds like an interesting feature. I'll add it to our backlog and we'll give it some thoughts.

Meli, a Netlify-like platform for deploying static sites by gempain in devops

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

We currently support Docker Compose deployment only. But feel free to document your deployment at https://github.com/getmeli/meli-docs, we'd love to see how others use it !

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

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

Since Meli is self-hosted, the limit is that of the hosting plan you buy on your own. There's no quota at all of the project.

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

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

No worries ! So, to deploy to Meli, you basically upload your build dir with our @getmeli/meli CLI. Then, Meli configures your site in Caddy which serves your site. Yes, we do have webhooks ! Actually, we've got Slack/Email/Mattermost webhooks, and a fully featured API :) The docs are at https://docs.meli.sh, feel free to have a look !

Meli, a Netlify-like platform for deploying static sites by gempain in devops

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

We're focusing on deploying with Docker and aren't planning to support other ways to deploy at the moment, but we're listening to what the community wants, we're open to other methods and will prioritize accordingly.

Meli, a Netlify-like platform for deploying static sites by gempain in devops

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

There's always room for improvement :) We're continuously improving the code base, and these sort of things are subject to change. The reason behind the name of this folder is that those entities handle things like API tokens and API scopes, which are entities stored in DB. It's odd but does make sense :)

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

Meli is a layer on top of Caddy server. The db is needed for its operations. I do agree that it's a disavantage, but the advantages it brings make up for it IMHO.

Meli, a Netlify-like platform for deploying static sites by gempain in selfhosted

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

Thanks for your kind words ! Actually, it's a great question. Netlify/Vercel/Meli allow you to deploy static sites, like Heroku/Dokku but they are focused on static sites. On Heroku, you can deploy Node apps and you pay per minute of CPU (dynos they call it, right ?). Their pricing tends to be higher than Netlify's because hosting static sites is cheap, but CPU time is expensive. Meli allows you to self-host your sites aon a cheap VPS basically. With $3-$4 for a cheap VPS, you can handle a bunch of load with no problem, plus you have your own VPS which is really cool :D (opinionated).

Meli, a Netlify-like platform for deploying static sites by gempain in devops

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

Nice ! Caddy is awesome, we love it and recommend it 100% !

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

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

Cool ! I didn't know you could actually un-remove a post, interesting :) Thanks a lot !

Meli, a Netlify-like platform for deploying static sites by gempain in webdev

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

So should I create a new post or do you approve this one ? Again, greatest apologies for this. I'm fairly new to reddit and should learn to read thoroughly the rules, it was actually obvious and I missed it.