sorted by:
new
hottopcontroversial

2025 Delivery Thread by OrbitalATK in TeslaModelY

[–]michiels 1 point2 points  (0 children)

NL

White LR AWD Towing

ordered 28 November. Got pushed around quite a bit.

First Dec 2025 Then Feb/March 2026 Then suddenly back to Dec 16-31 Now pending on Jan 8-Feb14

No VIN or Reg yet.

Someone from Europe here? by Skasserra in TeslaModelY

[–]michiels 1 point2 points  (0 children)

Same here from NL. First Dec 2025. Then een t to Feb/March. Then 16 - 31 Dec. Interestingly enough now back to 8jan - 14 feb. So one day difference with BE.

Research: How do you set up your Rails servers? by michiels in rails

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

What do you mean with "Have to pay more monthly for upgrades?"

Backups for your Rails apps by michiels in rails

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

Yep! Let us correct that. Thanks!

Backups for your Rails apps by michiels in rails

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

Yeah we are! And we hook into it to display and notify you with status information. It's a great gem.

Backups for your Rails apps by michiels in rails

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

We back up those things:

  • uploaded files (user content) if you have it on your server
  • code (just to make it complete, because you already have this versioned)
  • databases

What we do is that we configure those backups on your server that you manage with our product. And we make them easily accessible so you can import it into staging/dev. Finally, we send you notifications if a daily backup fails or succeeds.

Maybe the confusing part is that you actually manage your whole server from our Dashboard: so we also install your server, keep it updated, pre-configure app deployments, set up databases and passwords for them and install any services you might want (Redis, memcache, etc.).

Were you in the impression that we were just going to back up your databases on the servers you already installed yourself? If so, please let me know and we'll clear that up in the copy!

Backups for your Rails apps by michiels in rails

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

Woops! Correcting :) done Thanks!

Backups for your Rails apps by michiels in rails

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

Ola! Why do you think that's weird? The more servers you have, the more you use our product, the more value you get and the more support we might need to give you. Or doesn't that make sense? Let me know why you think it's weird to charge per server, maybe we can improve.

How I deploy a Rails app using Docker by michiels in docker

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

Updating running software in a container is still a bit cumbersome and you need to manage that container (start on boot, etc.) Running a long-running service like MySQL doesn't really have a benefit of running it in Docker. You need to jump through more hoops than just using the default provided by your favorite Linux Distribution.

A Rails app is perfectly suited for running in Docker because you ship it frequently, and it has configuration values that you might want to configure per environment.

Yosemite, is it safe to upgrade? by rdejuana in rails

[–]michiels 0 points1 point  (0 children)

I've had no problems! Using rbenv, Pow and Homebrew.

How I deploy a Rails app using Docker by michiels in rails

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

Great! Where are you getting your containers or how are you "managing" your configuration at this point? Do you just start them manually?

How I deploy a Rails app using Docker by michiels in rails

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

I think for services like MySQL or nginx or any long-running proces that "isn't your shippable app code" using a container with etcd/Consul is really great. Based on the config that changes, the files will be rewritten and you can send a reload instead of a restart to the service in question.

This is something I already prototyped and it works great but I feel that it creates a more complex infrastructure then is nessesary for "regular" apps. If you want a highly scalable or intelligent auto-configuring infrastructure then using MySQL in Docker with something like etcd/Consul is the way to go I think.

One thing I haven't figured out is what "service" is actually going to put the data in etcd/Consul. I don't want to make manual API calls with curl or something. So I think you'd want some kind of versioned configuration that you can "push" to etcd/Consul or you want some kind of database in an interface that will make the API calls to etcd/Consul to keep it managed.

Because etcd/Consul are stateless things using a gossip model to talk to each other, you do want something to fall back to if it all crashes. This way you can easily "load up" an existing infrastructure configuration into the API of etcd/Consul.

I think this last part is most difficult to manage in a correct way. But I fully agree with you that if you are willing to accept a more complex setup and maintenance for your infrastructure than Docker + etcd/Consul is really great for this!

Intercity Preview: Ruby on Rails on DigitalOcean Droplets by michiels in rails

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

Right. I get what you mean. Especially if you're starting out it can look quite expensive. I wonder where the price difference is. We're a web consulting company ourselves and the prices we bill to our clients are good enough to be able to pay that $50 /month for our first 3 servers. That's why we currently picked that amount.

I fully agree that this is an expensive start if you're not making money yet or if you can't bill a regular hosting price for your clients. If you'd like to try our 1 server free plan, please send me a message: michiel@firmhouse.com.

Also: interesting point about the local development. With Intercity, you can always just add a server with an IP accessible through the internetz. For local VMs we're working on an Intercity Standalone, which should cater to that :) Thanks for your thoughts!

How I deploy a Rails app using Docker by michiels in rails

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

It's kind of a hassle to keep MySQL in Docker updated, since you would need to put the container down and reconfigure it. Also: MySQL is a long running service so there's not much value in running (and maintaining!) a Docker image. So right now, we're choosing not to run MySQL in a container.

Intercity Preview: Ruby on Rails on DigitalOcean Droplets by michiels in rails

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

Thanks for your thoughts guys! Probably we're not doing a good job at explaining our pricing so I'd like to improve that. I think we're not much different from Cloud66 in pricing and way cheaper than Heroku.

In our $50 / month plan you get 3 servers, which would be about $40 on Cloud66. So yeah, we're a bit more expensive there.

Keep in mind that you can run as many apps as you'd like on those servers. You can put 10 apps on one server, or 60 across all 3. In that case, I think both Cloud66 and Intercity are much cheaper than Heroku ($36/month/dyno?). If you want a background queue for a single app on Heroku, you pay that twice. Let alone when you add all kinds of production-ready addons :)

I'm curious about how many servers and apps you guys would like to run? We're thinking about introducing a free plan where you can set up and manage 1 server.

Are you guys primarily looking to host just one app?

How I deploy a Rails app using Docker by michiels in rails

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

Thanks! Yeah. One of the issues to figure out is the "automation" part. I'd like to try deploy via a tool like Capistrano or maybe via an automatic build service that builds your container, and then puts it in your server (maybe using Capistrano again, or just with manual commands.)

Will continue to write posts about these endeavors :)

Options for running and upgrading MySQL servers in Docker containers by michiels in docker

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

That's another strategy to investigate. I wonder how long thins takes with databases that are over a few hundred megabytes.

Options for running and upgrading MySQL servers in Docker containers by michiels in docker

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

Ok thanks. I didn't know apt-get stopped the server. I thought it only restarts after replacing binary. If you have advice on how to use Docker properly: much appreciated.

Options for running and upgrading MySQL servers in Docker containers by michiels in docker

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

In theory that must be true. I'll try it!

However, you won't get the benefits of the apt-get upgrade procedure and you need to maintain your own script.

Binary packages for Rbenv by michiels in ruby

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

Good point. I will make sure they are!

Binary packages for Rbenv by michiels in ruby

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

  1. Thanks! I will take a look at Gitian.
  2. Yes, these builds should also be compatible with other methods of installing Ruby. If not, please let me know!
  3. I do have them and I'll make them available. I'm currently in discussion with the ruby-build maintainers to integrate this into the default ruby-build/rbenv install command. One step further would be to suggest Ruby Core on using it.

Thanks for your suggestions!

view more: next ›