home.social

#scaleway — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #scaleway, aggregated by home.social.

  1. Well. I had to reinstall my computer (long story, stupid nvidia) so this time I installed #OpenCode on my computer, hooked it up to the qwen3.5 model at #Scaleway and added the VSCode integration. I am rather blown away. It's like having a really fast junior dev working for me. I asked it to read the code of the project and complete a simple role for #Ansible, which it did well, but made some odd module selections. I corrected it, it spat out the code I wanted. Like, 30 seconds and it's done.

  2. Nuevo proyecto cuando termine la serie de #PiezasPropias para la configuración de RocksDNS.

    Configurar servidor propio de element con Bridges para xmpp, irc, Signal, WhatsApp, Telegram, discord... Ahora mismo estoy mirando opciones y precios de #hertzner #ovh y #scaleway

    💃🏼 Lerelelele me meto en unos charcos..

  3. I have now completed transferring all my applications from #DigitalOcean to #Scaleway. Still got a couple minor things to sort out, but the bulk is done.

    Until 2 weeks ago, I have never had any problems with DigitalOcean. They provided good, stable, cheap not-exactly-big-tech cloud services that I have used personallt and professionally. I have a problem with their #government – personally, not speaking as a professional here.

    DigitalOcean is located in the #US, which has two problems that can no longer be ignored:

    1) the introduction of the #CLOUD act gives US governments rights to spy on any service provided by a US company, even if that is hosted elsewhere. This was a problem when enacted in 2018, and has become even worse in 2025 when the US demonstrated it is willing and able to abuse this power for political reasons.

    2) by paying for US cloud services, I am indirectly supporting the US. It is entirely #unethical to support the US, a hostile regime.

    Sure, this is not directly attributable to DigitalOcean; they may be as much as anybody else a victim of the US government. Sucks for them. Maybe do better at voting next time and elect a government that doesn't actively drive away customers?

    Oh, and two weeks ago, somebody at DigitalOcean rolled around in a pile of s̵h̵i̵t̵ #AI and smeared big stinking globs of t̵u̵r̵d̵ #LLM all over the cloud console, making it much worse to use, which is not a point in their favor, though #DigitalSoverignty is the main driver.
  4. I have now completed transferring all my applications from #DigitalOcean to #Scaleway. Still got a couple minor things to sort out, but the bulk is done.

    Until 2 weeks ago, I have never had any problems with DigitalOcean. They provided good, stable, cheap, not-exactly-big-tech cloud services that I have used personally and professionally. I have a problem with their #government – personally, not speaking as a professional here.

    DigitalOcean is located in the #US, which leads to two problems that can no longer be ignored:

    1) the introduction of the #CLOUD act gives US governments rights to spy on any service provided by a US-owned company, even if that is hosted elsewhere. This was a problem when enacted in 2018, and has become even worse in 2025 when the US demonstrated it is willing and able to abuse this power for #political reasons.

    2) by paying for US cloud services, I am indirectly supporting the US. It is entirely #unethical to support the US, a #hostile #regime.

    Sure, this is not directly attributable to DigitalOcean; they may be as much a victim of the US government as anybody else. Sucks for them. Maybe do better at voting next time and elect a government that doesn't actively drive away customers?

    Oh, and two weeks ago, somebody at DigitalOcean rolled around in a pile of s̵h̵i̵t̵ #AI and smeared big stinking globs of t̵u̵r̵d̵ #LLM all over the cloud console, making it much worse to use. This is absolutely not a point in their favor, though #DigitalSoverignty is the main driver for me leaving.
  5. I have now completed transferring all my applications from #DigitalOcean to #Scaleway. Still got a couple minor things to sort out, but the bulk is done.

    Until 2 weeks ago, I have never had any problems with DigitalOcean. They provided good, stable, cheap, not-exactly-big-tech cloud services that I have used personally and professionally. I have a problem with their #government – personally, not speaking as a professional here.

    DigitalOcean is located in the #US, which leads to two problems that can no longer be ignored:

    1) the introduction of the #CLOUD act gives US governments rights to spy on any service provided by a US-owned company, even if that is hosted elsewhere. This was a problem when enacted in 2018, and has become even worse in 2025 when the US demonstrated it is willing and able to abuse this power for #political reasons.

    2) by paying for US cloud services, I am indirectly supporting the US. It is entirely #unethical to support the US, a #hostile #regime.

    Sure, this is not directly attributable to DigitalOcean; they may be as much a victim of the US government as anybody else. Sucks for them. Maybe do better at voting next time and elect a government that doesn't actively drive away customers?

    Oh, and two weeks ago, somebody at DigitalOcean rolled around in a pile of s̵h̵i̵t̵ #AI and smeared big stinking globs of t̵u̵r̵d̵ #LLM all over the cloud console, making it much worse to use. This is absolutely not a point in their favor, though #DigitalSoverignty is the main driver for me leaving.
  6. I have now completed transferring all my applications from #DigitalOcean to #Scaleway. Still got a couple minor things to sort out, but the bulk is done.

    Until 2 weeks ago, I have never had any problems with DigitalOcean. They provided good, stable, cheap, not-exactly-big-tech cloud services that I have used personally and professionally. I have a problem with their #government – personally, not speaking as a professional here.

    DigitalOcean is located in the #US, which leads to two problems that can no longer be ignored:

    1) the introduction of the #CLOUD act gives US governments rights to spy on any service provided by a US-owned company, even if that is hosted elsewhere. This was a problem when enacted in 2018, and has become even worse in 2025 when the US demonstrated it is willing and able to abuse this power for #political reasons.

    2) by paying for US cloud services, I am indirectly supporting the US. It is entirely #unethical to support the US, a #hostile #regime.

    Sure, this is not directly attributable to DigitalOcean; they may be as much a victim of the US government as anybody else. Sucks for them. Maybe do better at voting next time and elect a government that doesn't actively drive away customers?

    Oh, and two weeks ago, somebody at DigitalOcean rolled around in a pile of s̵h̵i̵t̵ #AI and smeared big stinking globs of t̵u̵r̵d̵ #LLM all over the cloud console, making it much worse to use. This is absolutely not a point in their favor, though #DigitalSoverignty is the main driver for me leaving.
  7. Embeddings models from #Scaleway weren't working with #LiteLLM. Couple of hours of searching and testing, it's a three line fix. 😅

    github.com/BerriAI/litellm/pul

  8. Embeddings models from #Scaleway weren't working with #LiteLLM. Couple of hours of searching and testing, it's a three line fix. 😅

    github.com/BerriAI/litellm/pul

  9. Embeddings models from #Scaleway weren't working with #LiteLLM. Couple of hours of searching and testing, it's a three line fix. 😅

    github.com/BerriAI/litellm/pul

  10. Embeddings models from #Scaleway weren't working with #LiteLLM. Couple of hours of searching and testing, it's a three line fix. 😅

    github.com/BerriAI/litellm/pul

  11. Embeddings models from #Scaleway weren't working with #LiteLLM. Couple of hours of searching and testing, it's a three line fix. 😅

    github.com/BerriAI/litellm/pul

  12. Encore des hausses de prix chez OVHcloud et Scaleway… jusqu’à 600 % !
    next.ink/235675/encore-des-hau

    Vous avez des services chez #OVHcloud et/ou #Scaleway ? Mauvaise nouvelle, la saison des hausses de tarifs est loin d’être terminée. Le premier revoit ses hébergements web, avec trois gammes dont les tarifs après la première année peuvent être multipliés par trois. Chez Scaleway, des dizaines de services sont concernés, avec parfois jusqu’à fois sept sur les prix.

    #OVH

  13. Looking for provider in EU.
    or ?

    Any other recommendations?

  14. Anybody familiar with #Scaleway? How do you solve the following:

    1) reverse web-proxy, and
    2) compute instance backup?

    ad 1) I have a handful of compute instances, each running a web-application. They are on a private network without a public IP. I have a public gateway. I'd like to be able to access them via a browser, definitely using IPv4 and preferably with IPv6 too. I'm too cheap to add a public IP to each application. It seems the public gateway isn't enough (only forwards based on port and cannot do SNI), nor is edge services (only works with object storage and load balancers). I can set up an instance with an nginx/haproxy/envoy reverse proxy, but is there a better way?

    ad 2) I've a bunch of compute instances that I'd like to back up; preferably using a frequent snapshot and less frequent backup off-site. I'm not setting up a serverless function or cron job like some savage. What are good solutions? #weap.io looks neat but super sketchy (cannot find anything about ownership and their documentation was last updated 5 years ago). I use #Snapshooter now, and it works fine, but is #US owned.
  15. Suggestions? I have a bunch of services hosted at one cloud provider. They do not work well under #kubernetes, so they are hosted individually on small virtual machines (1 CPU, 1-2 GiB memory).

    I'm moving to another cloud provider, #Scaleway, who doesn't provide that small instances and (obviously) larger instances are more expensive. Also, Scaleway is charging quite a bit for public IPv4 addresses, so I'd either have to put them behind NAT (I already have that set up) or consolidate to reduce IP address use.

    What do?

    I could either eat the cost, host multiple services on a single VM, or set up another layer of virtualization to split out the machines, but neither option is particularly nice. Am I overlooking something obvious?

    The applications are #Pleroma (really #Akkoma), #Ghost, and #Peertube. Pleroma is written in Erlang, so it's not really possible to build Docker images for it. Last I looked, Peertube didn't have nice Docker images. Ghost does have a beta Dockerized version, so while I don't want to deal with that right now, I can just eat the cost for that temporarily.

    I've already picked a cloud provider, so using another one is not an option, and Scaleway's Stardust instances are not an option as you can only have one of those per region.
  16. Suggestions? I have a bunch of services hosted at one cloud provider. They do not work well under #kubernetes, so they are hosted individually on small virtual machines (1 CPU, 1-2 GiB memory).

    I'm moving to another cloud provider, #Scaleway, who doesn't provide that small instances and (obviously) larger instances are more expensive. Also, Scaleway is charging quite a bit for public IPv4 addresses, so I'd either have to put them behind NAT (I already have that set up) or consolidate to reduce IP address use.

    What do?

    I could either eat the cost, host multiple services on a single VM, or set up another layer of virtualization to split out the machines, but neither option is particularly nice. Am I overlooking something obvious?

    The applications are #Pleroma (really #Akkoma), #Ghost, and #Peertube. Pleroma is written in Erlang, so it's not really possible to build Docker images for it. Last I looked, Peertube didn't have nice Docker images. Ghost does have a beta Dockerized version, so while I don't want to deal with that right now, I can just eat the cost for that temporarily.

    I've already picked a cloud provider, so using another one is not an option, and Scaleway's Stardust instances are not an option as you can only have one of those per region.
  17. Suggestions? I have a bunch of services hosted at one cloud provider. They do not work well under #kubernetes, so they are hosted individually on small virtual machines (1 CPU, 1-2 GiB memory).

    I'm moving to another cloud provider, #Scaleway, who doesn't provide that small instances and (obviously) larger instances are more expensive. Also, Scaleway is charging quite a bit for public IPv4 addresses, so I'd either have to put them behind NAT (I already have that set up) or consolidate to reduce IP address use.

    What do?

    I could either eat the cost, host multiple services on a single VM, or set up another layer of virtualization to split out the machines, but neither option is particularly nice. Am I overlooking something obvious?

    The applications are #Pleroma (really #Akkoma), #Ghost, and #Peertube. Pleroma is written in Erlang, so it's not really possible to build Docker images for it. Last I looked, Peertube didn't have nice Docker images. Ghost does have a beta Dockerized version, so while I don't want to deal with that right now, I can just eat the cost for that temporarily.

    I've already picked a cloud provider, so using another one is not an option, and Scaleway's Stardust instances are not an option as you can only have one of those per region.
  18. Migration of infrastructure from external services to more private and EU based entities is going quite well, to name a few:

    1. Kubernetes clusters from Google K8S to @hetzner using terraform-hcloud-kube-hetzner

    2. Google cloud build to docker VM on

    3. Cloud features like storage, container registry and backups from google cloud to

    4. Email / Drive / Workspace to @protonprivacy

    5. LLMs to opensource/local instances (work in progress)

    6. Postman to Hoppscotch/Bruno

  19. Tout le monde semble se réjouir de la fin du lien entre le #HealthDataHub et Microsoft Azure... Ce genre de phrase a plutôt tendance à réveiller ma curiosité : "il semble que l’obtention de la qualification #SecNumCloud à la date de la mise en concurrence n’a pas été un pré-requis" (1).

    J'espère que ce n'est pas parce que #Scaleway est une filiale à 94,8 % du groupe Iliad (2), que cette décision a été prise.

    > Iliad > X. Niel > Macronie

    (1) lemondeinformatique.fr/actuali
    (2) fr.wikipedia.org/wiki/Scaleway

  20. Yeah oh joie ! Microsoft perd le contrat d'hébergement des données de santé des français au profit de #Scaleway , yala !

    https://www.01net.com/actualites/donnees-de-sante-des-francais-adieu-microsoft-bonjour-scaleway.html

  21. Philippe Latombe, député, annonce que la PDS (Plateforme des Données de Santé), alias le HDH (Health Data Hub) a fait le choix, pour l'hébergement de ses données, d'abandonner Microsoft Azure pour Scaleway.

    #Souveraineté #HDH #PDS #Scaleway #Cloud

  22. Philippe Latombe, député, annonce que la PDS (Plateforme des Données de Santé), alias le HDH (Health Data Hub) a fait le choix, pour l'hébergement de ses données, d'abandonner Microsoft Azure pour Scaleway.

    #Souveraineté #HDH #PDS #Scaleway #Cloud

  23. Philippe Latombe, député, annonce que la PDS (Plateforme des Données de Santé), alias le HDH (Health Data Hub) a fait le choix, pour l'hébergement de ses données, d'abandonner Microsoft Azure pour Scaleway.

    #Souveraineté #HDH #PDS #Scaleway #Cloud

  24. Philippe Latombe, député, annonce que la PDS (Plateforme des Données de Santé), alias le HDH (Health Data Hub) a fait le choix, pour l'hébergement de ses données, d'abandonner Microsoft Azure pour Scaleway.

    #Souveraineté #HDH #PDS #Scaleway #Cloud

  25. Philippe Latombe, député, annonce que la PDS (Plateforme des Données de Santé), alias le HDH (Health Data Hub) a fait le choix, pour l'hébergement de ses données, d'abandonner Microsoft Azure pour Scaleway.

    #Souveraineté #HDH #PDS #Scaleway #Cloud

  26. #Scaleway remporte l’hébergement des données de santé à la place de #Microsoft

    La ministre de la Santé a annoncé jeudi matin la sélection de Scaleway, filiale du groupe iliad, par la Plateforme des données de santé. Ce fameux « Health Data Hub », qui doit notamment faciliter l’accès aux données de santé à des fins de recherche, était précédemment hébergé par Microsoft.

    #FuckMicrosoft #BanMicrosoft #Privacy #RegainPrivacy #HealthDataHub #NoSpy #SouveraineteNumerique #NoGAFAM #BanGAFAM #GetTheGAFAMOutOfHere
    \o/
    sebsauvage.net/links/?UAiVLA

  27. #Scaleway remporte l’hébergement des données de santé à la place de #Microsoft

    La ministre de la Santé a annoncé jeudi matin la sélection de Scaleway, filiale du groupe iliad, par la Plateforme des données de santé. Ce fameux « Health Data Hub », qui doit notamment faciliter l’accès aux données de santé à des fins de recherche, était précédemment hébergé par Microsoft.

    #FuckMicrosoft #BanMicrosoft #Privacy #RegainPrivacy #HealthDataHub #NoSpy #SouveraineteNumerique #NoGAFAM #BanGAFAM #GetTheGAFAMOutOfHere
    \o/
    sebsauvage.net/links/?UAiVLA

  28. #Scaleway remporte l’hébergement des données de santé à la place de #Microsoft

    La ministre de la Santé a annoncé jeudi matin la sélection de Scaleway, filiale du groupe iliad, par la Plateforme des données de santé. Ce fameux « Health Data Hub », qui doit notamment faciliter l’accès aux données de santé à des fins de recherche, était précédemment hébergé par Microsoft.

    #FuckMicrosoft #BanMicrosoft #Privacy #RegainPrivacy #HealthDataHub #NoSpy #SouveraineteNumerique #NoGAFAM #BanGAFAM #GetTheGAFAMOutOfHere
    \o/
    sebsauvage.net/links/?UAiVLA

  29. #Scaleway remporte l’hébergement des données de santé à la place de #Microsoft

    La ministre de la Santé a annoncé jeudi matin la sélection de Scaleway, filiale du groupe iliad, par la Plateforme des données de santé. Ce fameux « Health Data Hub », qui doit notamment faciliter l’accès aux données de santé à des fins de recherche, était précédemment hébergé par Microsoft.

    #FuckMicrosoft #BanMicrosoft #Privacy #RegainPrivacy #HealthDataHub #NoSpy #SouveraineteNumerique #NoGAFAM #BanGAFAM #GetTheGAFAMOutOfHere
    \o/
    sebsauvage.net/links/?UAiVLA

  30. #Scaleway remporte l’hébergement des données de santé à la place de #Microsoft

    La ministre de la Santé a annoncé jeudi matin la sélection de Scaleway, filiale du groupe iliad, par la Plateforme des données de santé. Ce fameux « Health Data Hub », qui doit notamment faciliter l’accès aux données de santé à des fins de recherche, était précédemment hébergé par Microsoft.

    #FuckMicrosoft #BanMicrosoft #Privacy #RegainPrivacy #HealthDataHub #NoSpy #SouveraineteNumerique #NoGAFAM #BanGAFAM #GetTheGAFAMOutOfHere
    \o/
    sebsauvage.net/links/?UAiVLA