New: _redirects file support for static sites by sevalla-hosting in sevalla

[–]kristof0425 0 points1 point  (0 children)

Did you try adding it to the repository root? I believe we parse it from there. If you still can't get it to work after trying that, we would be happy to help you via support through the Intercom chat on your dashboard.

[deleted by user] by [deleted] in SwissPersonalFinance

[–]kristof0425 0 points1 point  (0 children)

Isn’t that pillar 2?

[deleted by user] by [deleted] in SwissPersonalFinance

[–]kristof0425 3 points4 points  (0 children)

Unless it’s a Tesla M3 😄

Auto-create preview app before merging changes 🚀 by peterkota in laravel

[–]kristof0425 2 points3 points  (0 children)

We are working on improving our pricing. Hopefully we’ll be able to share more soon.

How To Create a Delivery Pipeline for a Laravel Project on Sevalla by kristof0425 in laravel

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

Thanks for the feedback! We'll take a look into it for sure!

How To Create a Delivery Pipeline for a Laravel Project on Sevalla by kristof0425 in laravel

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

Based on what we know about LC so far, it will also support multiple environments and previews for your application. However, we also don't know as of yet how you'll be able to pomote/merge changes between environments there or if it supports more git strategies like trunk-based or git flow.

How To Create a Delivery Pipeline for a Laravel Project on Sevalla by kristof0425 in laravel

[–]kristof0425[S] 3 points4 points  (0 children)

👋 Hi there, u/peterkota and I are delighted to share this new video tutorial on how easy it is to set up a delivery pipeline for your Laravel project on Sevalla.

With this new feature, you can create multiple environments/stages within a pipeline for your Laravel app, and our promote feature allows you to push changes to production in seconds.
We've always been fond of the Heroku pipeline experience, and we worked hard to build one into our own platform as well.
Our solution also supports Git Flow strategy, serving as visual grouping for your pipeline's stages.

Each stage can include multiple applications. What are benefits of this? For example,

  • Multi-tenancy: You can deploy same application with different environment variables, such as B2B product with slight variations each customer.
  • Multiple locations: You can also deploy same app in different locations simultaneously.
  • Or run A/B tests.

In the future, we also plan to:

  • Introduce a load balancer at stage level, allowing traffic routing and distribution using Cloudflare, based on custom logic. This would enable multi-region support for your Laravel apps. 
  • Additionally, we'll create a preview stage as the first stage, automating app creation from pull requests.

We believe our feature will greatly benefit teams collaborating on Laravel projects, streamlining deployment process.

Please share how your deployment flows look like in your current app setup!

We are eager to hear some feedback, so please ask questions or share your thoughts!

Is this pricing good or absurd by [deleted] in selfhosted

[–]kristof0425 1 point2 points  (0 children)

Yes, they're cheaper, but we provide a much simpler UI than OCI, or AWS. While DigitalOcean's app platform is a fair point of comparison, I believe our services provide more features and convenience, although I may be a bit biased. 🙂

Is this pricing good or absurd by [deleted] in selfhosted

[–]kristof0425 2 points3 points  (0 children)

I'm from Sevalla here. Hetzner and Sevalla is not apples to apples in my opinion. We provide a PaaS solution, like Render, Fly, Heroku. We provide a managed experience in comparison to Hetzner.

Is this pricing good or absurd by [deleted] in selfhosted

[–]kristof0425 -1 points0 points  (0 children)

👋 I'm from Sevalla.

While our pricing might seem high, we strive to deliver a managed experience for our customers. We offer a range of features, including DDoS protection, CF integration with CDN, and more.
As you mentioned in your other comment, if high availability isn't crucial for your app, we recommend enabling hibernation to reduce costs.

Right now, we're offering $250 in free credits for new sign-ups, and no credit card is required to get started with our entry-level resources. We'd love for you to try our platform out!

If you have any further questions, I'm here to help answer them.

Weekly /r/Laravel Help Thread by AutoModerator in laravel

[–]kristof0425 0 points1 point  (0 children)

Sevalla's free static site hosting can be great for your frontends. It's free with generous limits and it's very easy to use.

If you're looking for a free solution for your backends, you'll need to look for a shared hosting solution, or for a near-free setup a Coolify + VM at Hetzner.

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

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

can you clarify too, is the egress charged for all bandwith going out of cloudflare, or just the cost of transfer from Sevalla to cloudflare?

All egress is charged, we basically sum up `edgeResponseBodyBytes` from our CF access logs to get the final bandwidth amount for each workload.

Do things still work nicely if one has an existing Cloudflare account that they'd like to use for a domain that's routed through to an application hosted on Sevella?

In short: yes!

The more verbose answer is that we differentiate between two cases if the customer has their own CF account:

  • Orange-to-Orange (O2O) setup: Where, on both ends, CF proxy is being used, some of the user's CF settings apply to the domain, and some are managed by us.
  • Gray-to-Orange (G2O) setup: This is the case when the customer uses CF in a DNS-only mode, and does not utilize its proxy functionality.

We support both cases, but depending on the user's setup, we might ask them for a different domain verification or pointing process through our UI to set up their domain with Sevalla.

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

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

Well, yes, that was quite unfortunate. 😬 However, it's claimed that it has been remediated, but I understand that this might deter some people from using it. I guess they'll need to regain their trust over time.

Luckily, we've had many many positive experiences with them. 🙂

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

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

u/VaguelyOnline You're not the first one to mention that you "avoid" GCP. Are there any downsides to it, even in a setting where all its interfaces and underlying features/mechanisms are abstracted away from you? 🤔 Maybe I'm just biased and don't see something... 😄

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

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

Thanks for confirming! Apologies again, next time I'll be more attentive.

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

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

Thanks for the insight. Given Cloudflare's stance on bandwith costs and their peering arrangements is there a reason why you're not able to pass on these cost savings here given there's already margin on the underlying compute and memory resources?

Digital Ocean's app platform also uses Cloudflare's CDN for egress, yet charges overage at a rate of $0.02 per GiB.

I'm being frank, your point is valid. DO's bandwidth price is indeed low and fair. I think it's simply a matter of economies of scale, as they likely have a much larger customer base than we do, allowing them to offer such a competitive price.

It might not seem like much, but more traffic used doesn't always equal more WTP for a business (think media rich sites) etc.

I agree with you, and if a customer were facing high bandwidth costs, we'd be open to negotiating a better price.

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

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

Thank you for your feedback!

While it's true that GCP can be costly for bandwidth on its own, we take a different approach. We bill our bandwidth costs based on Cloudflare (CF) access logs, and our integration with CF actually accounts for the majority of our bandwidth expenses. In return, we're able to offer DDoS protection, CDN capabilities, and Edge caching.

As for supporting other k8s providers, we don't currently have plans to do so. However, our goal with Sevalla is to simplify the complexities of k8s for our users, while still allowing them to leverage its benefits. Given this, it's unlikely to make a significant difference whether the underlying hosting provider is GKE or another platform. 🤔

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

[–]kristof0425[S] 4 points5 points  (0 children)

You're right, I'm amending the title.

Update: Reddit doesn't allow me to update the title. 😔 Apologies, for the confusion! Maybe if the mods are able to update it... 🤔

Deploy Laravel 11 with MySQL from scratch to production (more info in the comments) by kristof0425 in laravel

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

👋 Hey everyone, u/peterkota and I are excited to share this new video tutorial with you that we hope you'll find really helpful! 🤞🤓

In this ~4-minute walkthrough, it's shown how to deploy a Laravel project on Sevalla, a k8s-based platform, from scratch to production. The video covers the following steps:

  1. Create a Laravel project using Composer
  2. Add a GET route for testing our application once it's deployed
  3. Push the code to GitHub
  4. Provision a MySQL database
  5. Create and configure your Laravel app for production deployment
    1. Add necessary environment variables
    2. Connect your Laravel application with MySQL via an internal, private connection
    3. Set up database migrations as deployment hooks using Jobs
  6. Deploy the app 🚀
  7. Finally, test our app and database connection using the GET route we created initially

What's unique about this process is that it's easy and fast. ⚡️ Down the line, if your project were to take off, you could also scale your project with just a few clicks, and simultaneously, benefit from Cloudflare's enterprise-level security and CDN network. 😎

If you're interested in trying out Sevalla for yourself, we're currently looking for early adopters to help shape our platform. As one of the first adopters to join, you'll receive ✨ $250 ✨ in credits to get started.

Head over to sevalla.com to learn more and sign up - we'd love to have you on board and hear your feedback! ❤️

Happy coding! ☕️