plans = { 
      1.month => {standard: 10, pro: 50, enterprise: 100},
      1.year => {standard: 100, pro: 500, enterprise: 1000}
    }
    
    plans.each do |interval, details|
      details.each do |name, amount|
        Billing::Plan::Factory.find_or_create_by!(name: , interval:, amount:)
      end
    end

Comments URL: https://news.ycombinator.com/item?id=45594474

Points: 1

# Comments: 0

The resultant https://archive.org/download/fortressone-demos file browser left a bit to be desired. In particular I wasn't able to sort the files in reverse chronological order.

I wanted a better UI so vibe coded Internet Archive File Browser. It's a single HTML file with embedded JavaScript running on GitHub pages. Works for my purposes. Free and open source.

If you are an open source project and storing files that could reasonably be hosted for free on The Internet Archive this might be useful.

Enjoy.

Comments URL: https://news.ycombinator.com/item?id=43993393

Points: 4

# Comments: 1

https://www.fortressone.org

Many of the people captured in this video still play today and have enduring friendships.

Query complexity on the other hand requires knowledge, to make the query work and again to make it fast. But it won’t be urgent, and having made it work you will be a better developer.

Of course, sometimes we need to copy / cache etc. but avoid it if you can.

Comments URL: https://news.ycombinator.com/item?id=35596655

Points: 1

# Comments: 0

By 2005 (a very decent shelf life), the game was all but dead. This was a significant part of my life gone.

In 2018 I found the source, forked it and began FortressOne, a modern port of this classic game.

There are now a thousand people on our discord channel and daily games in four continents. I’m over the moon but more work needs to be done. This year my goal is to get it on steam.

Comments URL: https://news.ycombinator.com/item?id=33492602

Points: 1

# Comments: 0

I frequently need to re-provision new servers and close existing ones.

I've been doing all this with the help of docker-machine (now deprecated), and a collection of handy bash scripts. While this has worked, it's become more and more fragile and I need something better.

For years I've resisted Kubernetes because I keep hearing "premature optimisation", but at this point I'm not sure I have any other options. So before I dive head-long into Kuburnetes by what feels like necessity, how else could I possibly: - Push button provisioning of new hosts across a number of cloud providers - Monitoring so I can restart services under certain conditions. - Notification of failures etc. - Automatic / continuous deployment across all servers and regions.

Basically, name+unique_identifier@domain.tld

The unique_identifier is unique to this AWS account.