my product VS Coolify

[general] Duration = 0 # Stream indefinitely BufferSecs = 5 # Buffer for the input, in seconds Reconnect = yes # Reconnect to the server if disconnected [input] Device = default # Your audio capture device SampleRate = 44100 # Sample rate in Hz BitsPerSample = 16 # Bits per sample Channel = 2 # 2 = stereo, 1 = mono [icecast2-0] BitrateMode = cbr # Constant bit rate Format = mp3 # Audio format Bitrate = 128 #... - Source: dev.to / 5 days ago

It’s frustrating that even on notion paid plans, the best you can do is a notion.site subdomain like mywebsite.notion.site. Why can’t I just connect to mywebsite.com? Source: 7 months ago

I made more or less progress by adding the PathPrefixes to my router but it can't be the correct way to handle this as it could interfer with the service I host on the root of https://mywebsite.com . Source: 8 months ago

Var req = require('request')req("http://mywebsite.com", function(err, resp, body) { var output = // pull some interesting pieces out of the whole body console.log(output);}); The generation of my output variable is not central to the issue here. The relevant parts are that I use request to make an asynchronous call and use console.log to output my results... Maybe this is a problem? Source: 10 months ago

Mywebsite.com/?landing-facebook is what I'm attempting, but this takes me to mywebsite.com and not the mywebsite.com/landing page. Source: 11 months ago

Solutions like pocketbase and coolify come close to solving these problems. However, I wouldn't choose either as I fear architecture lock-in as much as vendor lock-in. Especially in the case of pocketbase, I may be forced to rewrite my application if it were to scale overnight. - Source: dev.to / 4 days ago

This is my first quick try deploying SvelteKit with the open source software Coolify by Andras Bacsai. - Source: dev.to / 18 days ago

With a serverful approach, you can avoid these drawbacks, and the main challenge lies in selecting the platform that aligns with your requirements. Options may include AWS, Render, DigitalOcean, and others. While VPS is also an option, it's generally not recommended due to the significant setup and maintenance overhead involved (logging, monitoring, CI/CD pipelines, etc.). However, you can make your life easier by... - Source: dev.to / about 1 month ago

Heroku and similar providers can simplify the server management issues, but you can use something much better that can combine both cost efficiency and ease of deployment—Coolify:. - Source: dev.to / about 2 months ago

> VPSs being “easy to manage” is a strong option full of assumptions. There are definitely many footguns with managing a VPS but I think the threshold to get vaguely competent with a VPS is not really that far off with getting familiar with the average cloud platform - which comes with its own dangers, like the near-total inability to put an upward cap on fees that that person found out with Netlify recently.... - Source: Hacker News / 3 months ago